Fix macOS framework bundle layout#59
Merged
Merged
Conversation
Kyle-Ye
changed the title
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.
Summary
Fixes the macOS framework bundle layout for private framework xcframework slices so Xcode 26 no longer rejects embedded frameworks with shallow
Info.plistfiles.Details
Versions/Current/Resources/Info.plistwith top-level framework symlinks.Root Cause
Xcode 26 validates macOS framework bundles as non-shallow bundles. Some macOS xcframework slices still placed
Info.plistat the framework root, which caused errors likeexpected Versions/Current/Resources/Info.plistwhen embedding frameworks in macOS example apps.Validation
plutil -linton all macOS frameworkVersions/Current/Resources/Info.plistfiles.xcodebuild -workspace Example/Example.xcworkspace -scheme AGExample -destination 'platform=macOS' -configuration Debug buildxcodebuild -workspace Example/Example.xcworkspace -scheme RBExample -destination 'platform=macOS' -configuration Debug buildxcodebuild -workspace Example/Example.xcworkspace -scheme CoreUIExample -destination 'platform=macOS' -configuration Debug buildxcodebuild -workspace Example/Example.xcworkspace -scheme SFSymbolsExample -destination 'platform=macOS' -configuration Debug buildCoreSVG has a macOS framework slice but no example scheme in this workspace, so its bundle layout and plist were validated directly.