Skip to content

[Due for payment 2026-08-27] iOS - 2FA - Blank screen is displayed after enabling 2FA #98519

Closed

Description

@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/52723519/41236669/1653444404?sort=%2Bidentifier
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: iOS
App Component: User Settings

Action Performed:

  1. Open the app
  2. Navigate to Account > Security > Two Factor Authentication (2FA)
  3. Save the file in the local machine
  4. Enter the 6 digit code provided by the authenticator app
  5. Click Next

Expected Result:

A success screen is displayed after enabling 2FA

Actual Result:

A blank screen appears briefly after enabling 2FA.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7232153_1786587008316.expensifail_account.mp4
Bug7232153_1786571941769.2FA_in_gmail_account.mp4

View all open jobs on GitHub

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

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 13, 2026
  2. melvin-bot commented on Aug 13, 2026

    @melvin-bot

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

  3. melvin-bot commented on Aug 13, 2026

    @melvin-bot

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

  4. github-actions commented on Aug 13, 2026

    @github-actions
    Contributor

    👋 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.
  5. MelvinBot commented on Aug 13, 2026

    @MelvinBot
    Contributor

    🔍 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.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:
      • patches/react-native/react-native+0.86.0+032+fix-recycled-view-stale-frame.patch
      • patches/react-native/react-native+0.86.0+013+fix-mask-persisting-recycling.patch
      • patches/react-native/react-native+0.86.0+005+resetAutoresizingOnView.patch
      • patches/react-native/react-native+0.86.0+025+fix-display-contents-dirty-flag.patch
    • Corroboration: sibling iOS deploy blocker [Due for payment 2026-09-02] iOS - Account - The page is greyed out when swiping back. #98493 ("The page is greyed out when swiping back") — another transient iOS rendering regression in this same release — was already investigated and attributed to upgrade react native to 0.86.0 #96372, with @roryabraham engaged on an upstream RN fix. This release also produced an unusually large cluster of blockers at once, a hallmark of a framework-level upgrade.

    Verification

    • 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.

  6. jakubstec commented on Aug 13, 2026

    @jakubstec
    Member

    i've tested the local build on my jakubstec/upgrade-to-rn-0.86 branch and it seems to be working fine there

    Screen.Recording.2026-08-13.at.08.43.55.mov

    edit: cannot reproduce it on main either on my local build

  7. 18 remaining items

  8. 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
  9. melvin-bot commented on Aug 20, 2026

    @melvin-bot

    @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]

  10. linhvovan29546 commented on Aug 27, 2026

    @linhvovan29546
    Contributor

    @mountiny @roryabraham Could you please reopen the issue? I need to be paid for this as well.

  11. melvin-bot commented on Aug 30, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  12. melvin-bot commented on Aug 30, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  13. linhvovan29546 commented on Aug 31, 2026

    @linhvovan29546
    Contributor

    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:

    • 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.

    Do we agree 👍 or 👎

  14. mallenexpensify commented on Sep 1, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @linhvovan29546 due $250 via NewDot

    Think we're good to close, comment or reopen if you disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions