Forage

If a build fails when compiling binaries during tuist cache, users often see in the CI logs only:

Something about the setup with assets inside of https://github.com/EmergeTools/SnapshotPreviews-iOS makes Tuist break when using this dependency.

When the XcodeKit framework is added to target dependencies, it’s set to Do Not Embed by default.

Using Path.relativeToCurrentFile results in the callerPath being appended with the value from #file, which is the absolute path to the file, which in turn invalidates the manif…

Problem description:

similar to https://github.com/tuist/tuist/issues/4095.

https://github.com/Datadog/dd-sdk-ios makes Tuist break when using this dependency.

I’m migrating an old project to Tuist.

When creating a project that has targets specifying .iOS as destination, I would expect the tuist cache command to generate xcframeworks for iOS simulator and device.

Hi, I’m not sure if this is really a bug or not, but I encountered differences when running tuist generate for targets and for tags in conjunction with the cache.