iOS - Account - The page is greyed out when swiping back.

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.53-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/68879268/folder/52724024/41237963/1653445195?sort=-identifier
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 13 iOS 26.6
App Component: Other

Action Performed:

1. Open the app
2. Navigate to Account
3. Tap Profile
4. Swipe back

Expected Result:

The page should remain fully visible and not appear greyed out when swiping back.

Actual Result:

The page is greyed out when swiping back.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7232025_1786562453536.ScreenRecording_08-12-2026_14-16-28_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7232025

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/92237a3c49ca1c83dde7a1a602e477d23a554d6a6a2d5ef6b8934c0105e5092f

[melvin-bot]

Triggered auto assignment to @yuwenmemon (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug (Expensify/App)
Causing PR: #96372 - "upgrade react native to 0.86.0" by @jakubstec (Medium confidence)
Related Issues: none identified

Recommendation: ROLL FORWARD

This is the React Native 0.85.3 → 0.86.0 core upgrade (plus Expo SDK 57 and a full re-port of the native patch stack). A full revert would also unwind the Expo bump, the Mobile-Expensify submodule alignment, and dozens of dependent native patches, which is far riskier than a targeted screen-transition fix. Keep DeployBlockerCash (App-only, iOS-only, staging-only regression).

Assigned: @jakubstec (PR author), @mountiny, @roryabraham (approving reviewers) from the highest-confidence causing PR only
Labels: No change. DeployBlockerCash kept (frontend/App bug). No DeployBlocker present to remove.

📋 Detailed Analysis

Evidence

• The bug is iOS App only, reproducible on staging but NOT production — so the cause is a PR in the current deploy (9.4.53-0, checklist Deploy Checklist: New Expensify 2026-08-12 #98463).
• The symptom (previous screen appears greyed/dimmed during the iOS interactive swipe-back gesture) is a native screen-transition rendering issue.
• The only change in this deploy that alters native screen/transition rendering is the RN core bump in upgrade react native to 0.86.0 #96372:

  -    "react-native": "0.85.3",
  +    "react-native": "0.86.0",
  

  (package.json#L181 @ merge commit)
• upgrade react native to 0.86.0 #96372 also re-ports the entire native patch set, dropping several 0.85.3 patches and renumbering/replacing them for 0.86.0 (e.g. ...019+fix-modal-transparent-navigation-bar.patch, ...005+resetAutoresizingOnView.patch, ...032+fix-recycled-view-stale-frame.patch). A behavioral change in how react-native-screens composites the revealed card during an interactive pop is consistent with an RN core bump.

Verification

• Screen-transition/interpolator source files were NOT touched in this deploy window (Aug 2026): enhanceCardStyleInterpolator.ts, useModalCardStyleInterpolator.ts, useRootNavigatorScreenOptions.ts, useSplitNavigatorScreenOptions.ts all last changed months earlier — ruling out a JS interpolator regression.
• react-native-screens, react-native-reanimated, react-native-gesture-handler, and @react-navigation/* versions did not change in package.json — the swipe-back transition stack itself is unchanged except for the RN core under it.
• upgrade react native to 0.86.0 #96372 is confirmed to modify package.json (RN/Expo/Metro versions) and the patches/react-native/* + patches/expo*/* set; merged 2026-08-10, before the 9.4.53 staging cut.

Secondary (lower-confidence) candidate

• #95391 "Migrate useSingleExecution off InteractionManager" touches TransitionTracker.ts, ScreenLayout.tsx, and TabNavigator. It is transition-timing related and could theoretically leave a transition-driven overlay in an intermediate state, but it does not change overlay opacity/backdrop rendering, so it is a weaker fit than the RN bump. Worth a look if the RN-side fix does not reproduce cleanly.

Root Cause

RN 0.86 changed native-side view compositing during the interactive card pop. During the iOS edge swipe-back, the screen being revealed underneath the popping card renders with a persistent dimming/overlay instead of at full opacity. Because the JS navigation config (screens/interpolators) is unchanged, the regression is in the upgraded native layer shipped by #96372.

Why ROLL FORWARD instead of REVERT

#96372 is a large, high-blast-radius upgrade (RN core, Expo SDK 57, Metro, full patch re-port, Mobile-Expensify submodule alignment). Reverting risks reintroducing whatever the paired Mobile-Expensify RN 0.86 changes depend on. A targeted patch/fix to the screen-transition overlay (owned by the SWM upgrade authors) is the safer path.