fix(cli): Compilation errors when a static framework contains resources#9141
Merged
fix(cli): Compilation errors when a static framework contains resources#9141
Conversation
dosubot
bot
added
size:M
pepicrft
changed the title
🛠️ Tuist Run Report 🛠️Tests 🧪
Builds 🔨
|
fortmarek
approved these changes
Jan 16, 2026
pepicrft
added a commit
that referenced
this pull request
Feb 13, 2026
This reverts the static framework resource embedding feature that was introduced across multiple PRs (#9081, #9141, #9210, #9240, #9317, #9382, #9419 and related fixes). Resources for static frameworks go back to being placed in separate .bundle targets instead of being embedded inside the framework itself. The cache version is bumped to invalidate artifacts built with the old embedding approach.
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A regression in 4.122.2 causes iOS 26 simulator installs to fail when a static framework with resources is embedded in the app bundle. The simulator reports:
Static frameworks are not valid runtime-embedded frameworks; iOS 26’s installer now validates embedded frameworks more strictly and rejects these bundles. This appears when a static framework includes resources and Tuist decides to embed it.
Reproduction
Generate the sample:
/Users/pepicrft/Downloads/CLImageEditorTuistSampleCLImageEditorTuistSample.zip
Build the app.
Install on iOS 26 simulator:
xcrun simctl install <device> <app>.appOn 4.122.2, install fails with the Info.plist validation error because the static framework is copied into
.app/Frameworks.Root cause
GraphTraverser.embeddableFrameworkstreated static frameworks that contain resources as embeddable, which drives the “Embed Frameworks” phase. That embeds the static framework into the app, and iOS 26 refuses to install it.Fix
Stop embedding static frameworks just because they contain resources. Static frameworks should only be embedded when they have Metal sources (because Metal generates
default.metallibthat must be packaged). This keeps the existing Metal exception but prevents invalid static framework embedding for resources.Tests
xcodebuild: schemes inTuist.xcworkspaceare not configured with the test action.mise run cli:lint --fixVerification
Rebuilt Tuist, regenerated the sample, built the app, and installed on iOS 26 simulator. The app no longer contains
.app/Frameworks, and install succeeds.