-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
fix: Fix iOS build issue on Xcode 16.3 #15045
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fixed my iOS builds (using xcode 16.3)
Skipping sonar cloud since function was not changed on files complaining about coverage |
|
|
Description
Fix iOS build issues on Xcode 16.3 by bumping Sentry and Expo deps. RN sentry package is bumped a major version from v5 -> v6, which introduced some breaking changes under the hood. This also updates pods repo so a few other minor version bumps will exist in Podfile.lock as well.
Related issues
Fixes:
Manual testing steps
How it was tested: Both Android and iOS apps should run after running
yarn start:ios
oryarn start:android
Screenshots/Recordings
Before
Individuals began experiencing iOS build issues with Xcode 16.3 as reported here - https://consensys.slack.com/archives/C02U025CVU4/p1746041871082239. The fix was to bump Expo SDK deps as well as Sentry.
Expo SDK deps - https://expo.dev/changelog/xcode-16-3-patches
Sentry issue - https://github.com/getsentry/sentry-cocoa/releases/tag/8.46.0 (we bumped to stable 8.48.0 with pod repo update)
Sentry spans were not associated correctly in v5

After
Spans are now correctly associated with the parent span with v6

Pre-merge author checklist
Pre-merge reviewer checklist