Hi all,
We just changed (in CLI 4.122.2) Tuist’s resource handling for static frameworks: Tuist will no longer generate a separate .bundle target for static frameworks. Instead, resources are always expected to live inside the static framework, in line with Xcode 15+ support for resource-bearing static frameworks (see Apple’s “Creating a static framework” doc).
Why this change:
- It removes the extra resource bundle target and the associated lookup logic.
- It aligns Tuist behavior with Apple’s guidance for static frameworks with resources.
- It simplifies runtime bundle discovery for static frameworks across platforms.
This builds on prior attempts to improve static framework resource handling. If you are curious, see the previous discussion here.
Please try this out and report any issues you find, especially on macOS or in mixed-platform workspaces. If something breaks, a minimal repro, the Xcode version, and the target type (static framework vs XCFramework) would be super helpful.
Thanks! The feedback will help us validate the change across different setups.