You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-08-27] iOS - 2FA - Blank screen is displayed after enabling 2FA #98519
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug (Expensify/App) Causing PR: #96372 - "upgrade react native to 0.86.0" by @jakubstec (Medium confidence) Related Issues: #98493 (iOS - page greyed out when swiping back — same class of RN 0.86 transition/rendering regression, already attributed to #96372), and a cluster of other blockers in this release (98490, 98502, 98504, etc.)
Recommendation: ROLL FORWARD
This is the React Native 0.85.3 → 0.86.0 core upgrade (63 files, plus dependent follow-up PRs #98293 and #98352 and Mobile-Expensify submodule bumps). A full revert is impractical and high-risk; the fix should be a targeted native patch for the iOS Fabric screen-transition / view-recycling behavior (the same approach being taken for sibling blocker #98493).
Assigned: @jakubstec (PR author), @mountiny and @roryabraham (approving reviewers) of #96372 Labels: No change. DeployBlockerCash is kept (an App PR caused this; the bug is an iOS-only staging regression). No DeployBlocker label was present.
📋 Detailed Analysis
Evidence
The bug is a staging-only regression (not reproducible in production), so it was introduced by a PR in the current 9.4.53 StagingDeployCash.
None of the files that render the 2FA success flow changed in this deploy. The latest commits touching DynamicVerifyPage.tsx, DynamicSuccessPage.tsx, SuccessPageBase.tsx, TwoFactorAuthWrapper.tsx, and ConfirmationPage.tsx all predate the production/staging merge-base (2026-08-10) and are already in production. The 2FA feature logic is therefore not the source.
The only systemic change in this deploy that fits an iOS-only, transient "blank screen briefly" during a native screen transition is the React Native 0.86.0 upgrade (upgrade react native to 0.86.0 #96372), which is the oldest merged PR in this release.
upgrade react native to 0.86.0 #96372 replaced the entire react-native+0.85.3+* patch set with react-native+0.86.0+* patches, several of which exist specifically to fix iOS Fabric view-recycling / stale-frame regressions introduced by 0.86 — the exact symptom class of a brief blank screen:
Affected user-visible area: the 2FA enablement success screen shown after entering the 6-digit code and pressing Next (Settings → Security → Two Factor Authentication), iOS App only.
Transition path (context, not the defect source): DynamicVerifyPage.tsx#L58-L63 calls Navigation.navigate(TWO_FACTOR_AUTH_SUCCESS, {forceReplace: true}), replacing the Verify screen with the Success screen in the RHP native stack. The brief blank appears during this native screen replacement on iOS under RN 0.86, before SuccessPageBase → ConfirmationPage paints.
Confirmed the version bump lands in this deploy: package.json#L181 → "react-native": "0.86.0" (was 0.85.3).
Root Cause
React Native 0.86.0 changed iOS Fabric view lifecycle/recycling behavior. When the RHP native stack performs a forceReplace (Verify → Success), the outgoing view is torn down and the incoming Success view is not yet painted, leaving a blank frame for a moment. The 2FA screens themselves are unchanged; they merely surface the general 0.86 transition regression that is also producing the other iOS blockers in this release.
changed the title [-][Due for payment 2026-08-21] iOS - 2FA - Blank screen is displayed after enabling 2FA[/-][+][Due for payment 2026-08-27] iOS - 2FA - Blank screen is displayed after enabling 2FA[/+]on Aug 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.56-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-27. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Test:
Open the app
Navigate to Account > Security > Two Factor Authentication (2FA)
Save the file in the local machine
Enter the 6 digit code provided by the authenticator app
Click Next
Verify, a success screen is displayed after enabling 2FA, not a blank page for a split second.
Activity
applause-bot commentedon Aug 13, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/6216ae45613409ccc3ccc9cefa24d4396e1bc84fa9cd7282e95314aa55fa9b61
https://platform.applause.com/services/links/v1/external/97c397dc0b964dd27621323d7b9195136409aacd2fafdfabe3f1fb84e00e36cd
melvin-bot commentedon Aug 13, 2026
Triggered auto assignment to @cristipaval (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 13, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Aug 13, 2026
👋 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:
MelvinBot commentedon Aug 13, 2026
🔍 Investigation Summary
Classification: Frontend bug (Expensify/App)
Causing PR: #96372 - "upgrade react native to 0.86.0" by @jakubstec (Medium confidence)
Related Issues: #98493 (iOS - page greyed out when swiping back — same class of RN 0.86 transition/rendering regression, already attributed to #96372), and a cluster of other blockers in this release (98490, 98502, 98504, etc.)
Recommendation: ROLL FORWARD
This is the React Native
0.85.3→0.86.0core upgrade (63 files, plus dependent follow-up PRs #98293 and #98352 and Mobile-Expensify submodule bumps). A full revert is impractical and high-risk; the fix should be a targeted native patch for the iOS Fabric screen-transition / view-recycling behavior (the same approach being taken for sibling blocker #98493).Assigned: @jakubstec (PR author), @mountiny and @roryabraham (approving reviewers) of #96372
Labels: No change.
DeployBlockerCashis kept (an App PR caused this; the bug is an iOS-only staging regression). NoDeployBlockerlabel was present.📋 Detailed Analysis
Evidence
DynamicVerifyPage.tsx,DynamicSuccessPage.tsx,SuccessPageBase.tsx,TwoFactorAuthWrapper.tsx, andConfirmationPage.tsxall predate the production/staging merge-base (2026-08-10) and are already in production. The 2FA feature logic is therefore not the source.react-native+0.85.3+*patch set withreact-native+0.86.0+*patches, several of which exist specifically to fix iOS Fabric view-recycling / stale-frame regressions introduced by 0.86 — the exact symptom class of a brief blank screen:patches/react-native/react-native+0.86.0+032+fix-recycled-view-stale-frame.patchpatches/react-native/react-native+0.86.0+013+fix-mask-persisting-recycling.patchpatches/react-native/react-native+0.86.0+005+resetAutoresizingOnView.patchpatches/react-native/react-native+0.86.0+025+fix-display-contents-dirty-flag.patchVerification
DynamicVerifyPage.tsx#L58-L63callsNavigation.navigate(TWO_FACTOR_AUTH_SUCCESS, {forceReplace: true}), replacing the Verify screen with the Success screen in the RHP native stack. The brief blank appears during this native screen replacement on iOS under RN 0.86, beforeSuccessPageBase→ConfirmationPagepaints.package.json#L181→"react-native": "0.86.0"(was0.85.3).Root Cause
React Native 0.86.0 changed iOS Fabric view lifecycle/recycling behavior. When the RHP native stack performs a
forceReplace(Verify → Success), the outgoing view is torn down and the incoming Success view is not yet painted, leaving a blank frame for a moment. The 2FA screens themselves are unchanged; they merely surface the general 0.86 transition regression that is also producing the other iOS blockers in this release.jakubstec commentedon Aug 13, 2026
i've tested the local build on my
jakubstec/upgrade-to-rn-0.86branch and it seems to be working fine thereScreen.Recording.2026-08-13.at.08.43.55.mov
edit: cannot reproduce it on main either on my local build
18 remaining items
[-][Due for payment 2026-08-21] iOS - 2FA - Blank screen is displayed after enabling 2FA[/-][+][Due for payment 2026-08-27] iOS - 2FA - Blank screen is displayed after enabling 2FA[/+]melvin-bot commentedon Aug 20, 2026
@linhvovan29546
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.56-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-27. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
linhvovan29546 commentedon Aug 27, 2026
@mountiny @roryabraham Could you please reopen the issue? I need to be paid for this as well.
melvin-bot commentedon Aug 30, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Aug 30, 2026
Payment Summary
Resolving PRs:
[CP Staging] fix iOS 2FA blank screen is displayed after enabling 2FA bug #98604
Follow-up: narrow useIsAgentAccount personal-details selector to avoid extra re-renders #98756
Contributor: @jakubstec does not require payment (Contractor)
Reviewer: @linhvovan29546 owed $250 via NewDot
BugZero Checklist (@mallenexpensify)
linhvovan29546 commentedon Aug 31, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR:
Link to discussion: https://github.com/Expensify/App/pull/98151/changes#r3891139863
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Test:
Do we agree 👍 or 👎
mallenexpensify commentedon Sep 1, 2026
Payment Summary
Contributor+: @linhvovan29546 due $250 via NewDot
Think we're good to close, comment or reopen if you disagree.