Fix iOS TTID crash by bumping Sentry React Native to 8.7.0

[marufsharifi]

Explanation of Change

This PR bumps @sentry/react-native from 8.2.0 to 8.7.0.

The reported iOS HybridApp crash happens in Sentry’s native Time To Initial Display path:

• SentryFramesTracker.displayLinkCallback
• RNSentryFramesTrackerListener
• RNSentryTimeToDisplay
• NSString stringByAppendingString

Sentry fixed this upstream in @sentry/react-native@8.7.0 via getsentry/sentry-react-native#5887 by synchronizing the native RNSentryTimeToDisplay state used during navigation TTID tracking.

This keeps the bump to the smallest version that includes the crash fix.

Fixed Issues

$ #95197
PROPOSAL: #95197 (comment)

Tests

• Verify @sentry/react-native resolves to 8.7.0

• Verify iOS Podfile.lock resolves RNSentry to 8.7.0

• Run npx patch-package --patch-dir patches

• Run iOS pod install for App / Mobile-Expensify as applicable

• Build or smoke test iOS HybridApp

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Screen.Recording.2026-07-14.at.5.45.45.PM.mp4

Android: mWeb Chrome

Recording_20260714_165130.mp4

iOS: Native

iOS: mWeb Safari

Screen.Recording.2026-07-14.at.6.38.33.PM.mp4

MacOS: Chrome / Safari

Screen.Recording.2026-07-14.at.4.45.51.PM.mp4

[github-actions]

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

[melvin-bot]

@Krishna2323 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[Krishna2323]

Why do we need this change?

[marufsharifi]

@sentry/react-native@8.7.0 references optional expo-updates, but we do not install/use it. Webpack tries to resolve it during web/Jest builds and fails.

'expo-updates': false tells webpack to treat that optional module as unavailable, avoiding an unnecessary native dependency.

[Krishna2323]

Please remove unrelated changes from this file.

[Krishna2323]

@marufsharifi I think the patches are not correctly regenerate.

[marufsharifi]

@marufsharifi I think the patches are not correctly regenerate.

Regenerated the patch. One stale patch file remained from the previous version, but it’s fixed now. Could you please check again? thanks

[Krishna2323]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e201ed7dc4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Add a native resolver/dependency for expo-updates

Bumping @sentry/react-native to 8.7.0 pulls in Sentry's new default expoUpdatesListenerIntegration, whose module contains a literal require('expo-updates'). This PR only aliases expo-updates in the webpack config, while the lockfile still has no node_modules/expo-updates entry and metro.config.js has no native resolver alias, so iOS/Android Metro bundling will try to resolve that missing module and fail before the integration's try/catch can run. Please add a compatible expo-updates dependency or a Metro/native no-op resolver alongside the web alias.

Useful? React with 👍 / 👎.

[Krishna2323]

@marufsharifi 👀 please

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/setup/telemetry/noopExpoUpdates.ts	0.00% <0.00%> (ø)
... and 13 files with indirect coverage changes

[marufsharifi]

@Krishna2323 Resovled Codex feedback, Could you please check again? thanks

[marufsharifi]

@Krishna2323 Gentle bump. thanks

[Krishna2323]

Reviewing...

[Krishna2323]

@marufsharifi I think the @sentry/core 001 patch still isn’t correctly regenerated. The patch content looks correct and applies fine, but the file itself wasn’t regenerated for 10.47.0 — it looks like it was renamed from the 10.39.0 patch.

The index hashes are still from 10.39.0 (3169c25 / 2ad52b0), whereas regenerating against 10.47.0 via patch-package gives 1bdc52f / 5e593f3 (same as we did for the 002 patch).

Could you please regenerate 001 properly with patch-package against 10.47.0? The 002 and browser patches look good.

[Krishna2323]

@MelvinBot review

[MelvinBot]

🤖 Review of the Sentry RN 8.2.0 → 8.7.0 bump. The change is well-scoped and the expo-updates shim approach is correct. One actionable item — the one Krishna2323 already flagged — plus one thing to double-check.

1. @sentry/core 001 patch not regenerated (confirmed)

Krishna2323's finding is correct. @sentry+core+10.47.0+001+data-sentry-label-support.patch was renamed from the 10.39.0 file but still carries the old blob hashes in its git index line (index 3169c25..19acc49), whereas the properly-regenerated 002 patch has fresh hashes. It applies fine today (the validate-patches check is green), so this is hygiene rather than a functional break — but please regenerate 001 with patch-package against 10.47.0 so the metadata matches 002 and future regenerations produce clean diffs.

2. Double-check the sentry-react-native patch (pure rename)

@sentry+react-native+8.7.0.patch is a similarity index 100% rename — the content is byte-identical to the 8.2.0 version. It patches the Sentry Ruby build script's RN path resolution. CI passing implies it still applies to 8.7.0, but since it was only renamed (not regenerated), please confirm the targeted .rb script is actually unchanged between 8.2.0 and 8.7.0 so we're not silently carrying a patch against a stale target.

3. expo-updates noop shim — verified correct ✅

I traced why this is needed and confirmed the shim is sound, so this doesn't need changes.

Why the shim is needed and why it's safe

8.7.0 adds a new expoUpdatesListenerIntegration that does a static require('expo-updates') (wrapped in try/catch). The try/catch handles the runtime "not installed" case, but Metro/webpack must still resolve the module at bundle time — a bare unresolved require is a build-time failure, not a catchable runtime error. That's exactly what this PR fixes:

• Native: metro.config.js maps expo-updates → noopExpoUpdates.ts.
• Web: webpack.common.ts aliases expo-updates → false (empty module).

Both are safe because the integration only consumes addUpdatesStateChangeListener / latestContext from the require, and:

1. setup() bails early via if (!isExpo() || isExpoGo()) return; — App is not an Expo-updates app, so the require is never even reached at runtime.
2. Even if reached, the shim intentionally omits addUpdatesStateChangeListener, so Sentry's typeof expoUpdates.addUpdatesStateChangeListener === 'function' check fails and it cleanly logs "expo-updates is not available, skipping." The empty-module (false) web alias behaves identically.

The shim's exports (isEnabled, updateId, channel, addListener, …) mirror expo-updates' real public API, which is a robust choice — it stays safe even if a future Sentry version reads those fields off the required module. Correctly added to knip.json ignore list.

Other notes

• Bumping the direct @sentry/core dep 10.39.0 → 10.47.0 to match what @sentry/react-native@8.7.0 pulls in is the right call — it avoids a duplicate @sentry/core in the tree.
• The sentry-browser 001 and sentry-core 002 patches were properly regenerated (updated hunk contexts + blob hashes). 👍
• ⚠️ Since this touches native libs, don't forget the AdHoc HybridApp build the bot flagged, given the whole point is fixing an iOS HybridApp crash.

---

Net: approve-able once the sentry-core 001 patch is regenerated (item 1) and the react-native patch target is confirmed (item 2).

[marufsharifi]

Could you please regenerate 001 properly with patch-package against 10.47.0? The 002 and browser patches look good.

@Krishna2323

Sorry for the miss here. I had previously regenerated with npx patch-package @sentry/core --patch-dir patches/sentry-core, but since the existing split patch files were already present, only the 002 patch got refreshed and the stale 001 metadata remained. I didn’t catch that at the time.

I removed the stale 001 patch, regenerated against @sentry/core@10.47.0, then split the generated patch back into the existing numbered files. Now the 001 diff only updates the index hashes to the regenerated 10.47.0 values.

Could you please check and confirm if it looks okay now? Thanks!

[marufsharifi]

2. Double-check the sentry-react-native patch (pure rename)
   @sentry+react-native+8.7.0.patch is a similarity index 100% rename — the content is byte-identical to the 8.2.0 version. It patches the Sentry Ruby build script's RN path resolution. CI passing implies it still applies to 8.7.0, but since it was only renamed (not regenerated), please confirm the targeted .rb script is actually unchanged between 8.2.0 and 8.7.0 so we're not silently carrying a patch against a stale target.

I checked the clean npm packages for @sentry/react-native@8.2.0 and 8.7.0. The patched target file scripts/sentry_utils.rb is identical in both versions, with the same SHA, so the rename is safe and the patch is not stale.

[Krishna2323]

@marufsharifi, could you please add the recordings? Just to make sure everything works correctly across all platforms.

[Krishna2323]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

android_hybrid.mp4

Android: mWeb Chrome

android_mWeb.mp4

iOS: HybridApp

ios_hybrid.mp4

iOS: mWeb Safari

ios_mWeb.mp4

MacOS: Chrome / Safari

web_chrome.mp4

[Krishna2323]

@marufsharifi please ping when you have added the recordings, this is ready to be approved once that's done.

[Krishna2323]

LGTM!

[marufsharifi]

@mountiny Please don’t merge this yet. I’m going to retest it again and will let you know once it’s ready. Thanks!

[mountiny]

@marufsharifi ping me in slack when ready

[github-actions]

🚧 mountiny has triggered a test Expensify/App build. You can view the workflow run here.

[mountiny]

@marufsharifi any updates?

[marufsharifi]

@mountiny, that's done. thanks.

[github-actions]

🚧 mountiny has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #95501 Mobile-Expensify PR Expensify/Mobile-Expensify#14002.

Android 🤖	iOS 🍎
❌ FAILED ❌	❌ FAILED ❌
The QR code can't be generated, because the Android build failed	The QR code can't be generated, because the iOS build failed

Web 🕸️
https://95501.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[marufsharifi]

@Krishna2323 I retested the iOS standalone build from a fresh setup after clearing caches, reinstalling node_modules, reapplying patches, reinstalling pods, and clearing DerivedData. It builds successfully for me locally now.

The PR build is still failing though. Could you please also test the branch locally on your side and confirm whether the iOS standalone build works for you too?

REC-20260718110054.mp4

[mountiny]

@marufsharifi the CI build is Hybrid App build, does that work for you?