revert(cli): revert static framework resource embedding#9446
Merged
Conversation
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.
dosubot
bot
added
the
size:XXL
|
Related Documentation Checked 1 published document(s) in 1 knowledge base(s). No updates required. How did I do? Any feedback? |
🛠️ Tuist Run Report 🛠️Previews 📦
Tests 🧪
Builds 🔨
Bundles 🧰
|
fortmarek
approved these changes
Feb 13, 2026
XcodeGraph 1.31.0 changed staticFramework to return supportsResources=true. The ResourcesProjectMapper needs to create separate resource bundles for static frameworks regardless, so add explicit staticFramework checks. Also update hash expectations and fix lint issues.
fortmarek
added a commit
that referenced
this pull request
Feb 19, 2026
PR #9446 (revert static framework resource embedding) accidentally removed the resolvingSrcRootPaths logic from PR #9203 that corrects $(SRCROOT)-relative paths when propagating settings from cached targets at different project paths. Without this fix, FRAMEWORK_SEARCH_PATHS and HEADER_SEARCH_PATHS for external static xcframeworks are computed relative to the cached target's location (.cache/tuist/Binaries/HASH/) instead of the consuming app's project directory, producing broken paths. Co-Authored-By: Claude Opus 4.6 <[email protected]>
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.
Summary
This reverts the static framework resource embedding feature introduced across PRs #9081, #9141, #9210, #9240, #9317, #9382, #9419, and their related fixes. Static framework resources go back to being placed in separate
.bundletargets rather than being embedded directly inside the framework.The approach of embedding resources inside static frameworks caused enough edge cases and regressions that we're reverting to the previous well-tested behavior while we rethink the approach. The cache version has been bumped to invalidate artifacts built with the embedding approach.
Test plan