Fix manifest paths for macOS app resource bundles - #3
Merged
Merged
Conversation
technoir42
enabled auto-merge (squash)
September 11, 2026 00:08
technoir42
disabled auto-merge
September 11, 2026 00:08
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
1 participant
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.
macOS SwiftPM resource bundles place manifests under
Contents/Resources, but the package paths assumed flattened bundles. Correct the three macOS driver/layer paths so standard Xcode apps can load their embedded libraries without rewriting manifests.Remove the sample’s bundle-flattening phase, discover resources through
Bundle.resourceURL, and verify path resolution for macOS and iOS app layouts. Document the supported packaging layout.Validation:
make cipassed (platform builds, signing tests, 27 Swift contract tests, and macOS/iOS simulator probes with validation enabled). An independent native Xcode consumer also built and ran with validation enabled and all three macOS manifest paths resolving, with no flattening or manifest-rewriting phase.