Forage

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:

When a target is a static library with a String Catalog resource file, this file is bundled with the automatically generated companion bundle. While this ensures that localizat…

I use Amplitude SDK, which doesn’t contain any Swift code, only headers. When I try to compile project I catch multiple errors like `Could not find or use auto-linked library ’swif…

Message

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.

Some keys that are similar can conflict with each other.

When an SPM package’s library product wraps both a source target and a binary target (where the binary is a dynamic xcframework), Tuist’s XcodeProj-based integration links …