Repository navigation
ci(ios): Archive the SwiftPM app to catch xcframework signature collisions - #6871
Merged
Merged
Conversation
…sions The archive step collects xcframework signatures into `Signatures/`. A second copy of the Sentry signature fails the archive, and a plain build does not show this. Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog.
🤖 This preview updates automatically when you update the PR. |
alwx
marked this pull request as ready for review
October 12, 2026 11:53
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.
📢 Type of change
📜 Description
The SwiftPM CI job now archives the app for iOS devices in the
productionmatrix entry. The job then makes sure that the archive contains the app binary and theSentry.xcframeworksignature.💡 Motivation and Context
Only the archive step collects xcframework signatures into
Signatures/. If two targets supply the Sentry signature, the archive fails, but a plain build passes. Users found this collision in the oldSENTRY_USE_SPM=1path (see the comment in #6174), and CI did not test it for the SwiftPM autolinking path from #6784.💚 How did you test it?
I did the CI steps locally with React Native 0.87.1 and Xcode 26.1. The archive passed, and Xcode collected the Sentry signature one time.
📝 Checklist
sendDefaultPIIis enabled.🤖 Generated with Claude Code