Repository navigation
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: v9.3.83-3
Reproducible in staging?: Needs Reproduction (Unable to reproduce with regular 2FA authentication)
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @Tmjarnesk1
Slack conversation (hyperlinked to channel name): #Expeisify Bugs
Action Performed:
- User attempts to log in with new-domain email
- User is routed to the onboarding page with the message “Two-factor authentication required.”
- User selects “Enable two-factor authentication.”
- Nothing happens; the button does not respond.
- User tries clearing cache, using a different browser, and using a mobile device.
- User remains blocked from completing 2FA setup and cannot access the new-domain account.
- Because the user cannot access the new-domain account, they also cannot complete the required account merge after domain migration.
Expected Result:
User should be able to click “Enable two-factor authentication,” complete 2FA setup, log in with the new-domain account, and merge the old email/account via Settings > Account > Profile > Merge Accounts.
Actual Result:
The “Enable two-factor authentication” button is unresponsive. User cannot complete 2FA setup, cannot access the new-domain account, cannot merge accounts, and cannot forward receipts from the new-domain email.
Workaround:
Unknown
Additional Context:
- Domain migration was completed.
- Migration note stated that user already had an Expensify account using the new-domain email.
- User was instructed to log in with the new-domain email, then go to Settings > Account > Profile > Merge Accounts to merge the old email into the new account.
- Issue only occurs when logging in with the new-domain email.
- User can access the old-domain login.
- Domain settings require 2FA, so the user is correctly prompted for 2FA, but the setup flow is blocked.
- This does not appear to be a standard 2FA reset case unless the new-domain account is in a partially enabled/broken 2FA state.
Platforms:
Select the officially supported platforms where the issue was reproduced:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
Screenshots/Videos
The screenshot with the console log is in Slack thread
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022060024083406042078
- Upwork Job ID: 2060024083406042078
- Last Price Increase: 2026-06-11
Issue Owner
Current Issue Owner: @thelullabyyMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
MelvinBot commentedon May 28, 2026
Proposal
What is the root cause of that problem?
When a domain-migration user logs in and hasn't completed onboarding, the
RequireTwoFactorAuthenticationOverlayrenders on top of the onboarding screens. Pressing "Enable two-factor authentication" callsNavigation.navigate(getTwoFactorAuthRoute()), which builds a dynamic route viacreateDynamicRoute.The navigation is silently blocked by the
OnboardingGuard.shouldPreventReset. Here's how:linkToparses the dynamic route. WhengetActionFromStatereturnsnullfor the generated path, it falls back tonavigation.resetRoot(stateFromPath), dispatching aRESETaction.OnboardingGuard.shouldPreventResetsees the user is on an onboarding screen and the target is a non-onboarding screen (the 2FA setup page), so it blocks the RESET and sets an error message on the onboarding screen — which is hidden behind the overlay. The user sees nothing.isIn2FASetupFlowstaysfalse, the overlay remains visible, and every subsequent tap is blocked the same way.What changes do you think we should make in order to solve the problem?
The
OnboardingGuard.shouldPreventResetfunction should allow RESET actions that target 2FA setup screens. The fix should check whether the target focused route is a 2FA setup screen (using the existingisTwoFactorSetupScreenhelper fromNavigation.ts) and, if so, allow the reset instead of blocking it.The change is in
OnboardingGuard.ts:shouldPreventReset: before returningtrueto block the reset, add a check — if the target route is a 2FA setup screen, returnfalse(allow it).What alternative solutions did you explore? (Optional)
An alternative would be to modify the overlay's
handleOnPressto bypass the normalNavigation.navigatepath (e.g., usingnavigation.dispatchwith a custom action that skips guards). However, this would be fragile and circumvent the guard system rather than fixing the actual conflict. Teaching the guard to recognize 2FA navigation as legitimate is cleaner and more maintainable.Supporting evidence
Key files:
RequireTwoFactorAuthenticationOverlay.tsx:55-57— button handleruseTwoFactorAuthRoute.ts:26-36— route resolution (unvalidated accounts go to verify-account)OnboardingGuard.ts:117-132—shouldPreventResetblocks non-onboarding targetslinkTo/index.ts:158-163— fallback toresetRootwhengetActionFromStatereturns nullData flow:
account.needsTwoFactorAuthSetup=truefor domain-migration useruseShouldShowRequire2FAPage→ overlay renders on top of onboardingNavigation.navigate(dynamicRoute)linkTo→getActionFromStatereturns null →resetRootdispatchedOnboardingGuard.shouldPreventReset→ blocked (onboarding → non-onboarding)Possibly related issue: #86194 covers a similar area (2FA + onboarding interaction) but focuses on showing a descriptive error rather than fixing the blocked navigation.
Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/91985#issuecomment-new)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
yusufdeveloper2903 commentedon May 28, 2026
Please re-state the problem that we are trying to solve in this issue.
On a domain that enforces 2FA, a user logging in with the new-domain email lands on the full‑screen "Two-factor authentication required" gate, but tapping Enable two-factor authentication does nothing — the 2FA setup flow never opens, so the user can't complete setup, log in, or merge accounts. It is not reproducible with a "regular" already-onboarded 2FA account.
What is the root cause of that problem?
The required-2FA gate was rewritten in #90680 (merged 2026-05-25, three days before this report) as the full-screen
RequireTwoFactorAuthenticationOverlay.Its button handler computes the target route with no
backToargument:https://github.com/Expensify/App/blob/d93353fd47faf/src/pages/RequireTwoFactorAuthenticationOverlay.tsx#L55-L57
getTwoFactorAuthRoute()builds the 2FA target as a dynamic route for the not-yet-enabled cases:https://github.com/Expensify/App/blob/d93353fd47faf/src/hooks/useTwoFactorAuthRoute.ts#L26-L36
A dynamic route is a suffix appended to a base path. When
backToisundefined,createDynamicRoutefalls back toNavigation.getActiveRoute()as that base:https://github.com/Expensify/App/blob/d93353fd47faf/src/libs/Navigation/helpers/dynamicRoutesUtils/createDynamicRoute.ts#L62-L71
The overlay is rendered as an absolute-fill sibling on top of the whole RootStack, so the base is simply whatever screen happens to sit behind it:
https://github.com/Expensify/App/blob/d93353fd47faf/src/libs/Navigation/AppNavigator/AuthScreens.tsx#L378-L379
So the navigation target is
<screen-behind-the-overlay>/two-factor-auth/verify-account. For a brand-new / just-migrated account being walked through onboarding, the screen behind the overlay is the onboarding flow (or a transitional, report-less Home), and that base does not host the dynamic 2FA suffix —getStateFromPathcan't resolve<onboarding>/two-factor-auth/verify-accountinto a valid 2FA state, soNavigation.navigateno-ops and the press is logged but visibly "does nothing" (matching the console-log screenshot in Slack).For a regular 2FA prompt (e.g. the still-used
ConnectToXeroFlow, or an already-onboarded admin), the active route is a normal resolvable screen —settings/report— so the very sameNavigation.navigate(getTwoFactorAuthRoute())resolves and works. That is exactly why this is "Unable to reproduce with regular 2FA authentication": the bug is in the base the dynamic route is anchored to, which only goes wrong when the gate floats over the onboarding/empty-account context.What changes do you think we should make in order to solve the problem?
Anchor the 2FA dynamic route to a stable, always-resolvable base instead of the transient screen behind the overlay, by passing an explicit
backTotogetTwoFactorAuthRoute.In
src/pages/RequireTwoFactorAuthenticationOverlay.tsx:const handleOnPress = () => { - Navigation.navigate(getTwoFactorAuthRoute()); + Navigation.navigate(getTwoFactorAuthRoute(ROUTES.SETTINGS_SECURITY)); };(
ROUTES.SETTINGS_SECURITY=settings/security, so the target becomessettings/security/two-factor-auth/verify-account— the screen 2FA naturally lives under, guaranteed to resolve regardless of what is behind the overlay, and giving the setup flow a sane return target.)src/pages/RequireTwoFactorAuthenticationOverlay.tsxonly (addROUTESimport).useTwoFactorAuthRoute(itsbackToparam already exists and is used byConnectToXeroFlow), the dynamic-route machinery, or thevalidated/requiresTwoFactorAuthbranching — the regular/Xero path stays byte-for-byte identical.verify-accountfor unvalidated accounts andtwo-factor-authroot for validated ones) since both go through the samecreateDynamicRoute(path, backTo).Once navigation succeeds, the overlay auto-hides because the focused screen becomes a
SET_UP_2FA_SCREENSmember, soisIn2FASetupFlowflips true (existing logic, no change needed).Test: Log in to a domain-enforced-2FA account that still needs setup while in the onboarding/new-account context, tap Enable two-factor authentication, and confirm the 2FA setup flow opens and can be completed.
What alternative solutions did you explore? (Optional)
Navigation.getActiveRoute()when the overlay first mounts and pass that asbackTo. Rejected because the active route during onboarding is itself the broken base — snapshotting it doesn't make it a valid host for the 2FA suffix.RootStack.Navigator. Correct long-term, but a much larger navigation change for what is a one-line anchoring bug; out of scope for the regression fix.getStateFromPath/createDynamicRouteto fall back to a default base. Rejected — it hides the real issue (the caller passing an unsuitable base) and risks masking other dynamic-route callers; fixing it at the call site is the surgical fix.David-2002065 commentedon May 28, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When a user is forced onto the "Two-factor authentication required" screen, clicking Enable two-factor authentication does nothing — the button is unresponsive and the user cannot complete 2FA setup, which blocks the new-domain login and account merge after domain migration.
What is the root cause of that problem?
The "Two-factor authentication required" screen is
RequireTwoFactorAuthenticationOverlay. The button callshandleOnPress, which navigates to whatevergetTwoFactorAuthRoute()returns:https://github.com/Expensify/App/blob/main/src/pages/RequireTwoFactorAuthenticationOverlay.tsx#L55-L57The overlay itself is a full-screen
StyleSheet.absoluteFillthat only un-mounts whenshouldShowRequire2FAPagebecomes false or the focused screen is in the 2FA setup flow:https://github.com/Expensify/App/blob/main/src/pages/RequireTwoFactorAuthenticationOverlay.tsx#L59-L70shouldShowRequire2FAPageis true under either of two conditions:https://github.com/Expensify/App/blob/main/src/hooks/useShouldShowRequire2FAPage.ts#L10-L15So the overlay can be visible even when
requiresTwoFactorAuthistrue— via the second clause (twoFactorAuthSetupInProgress && !hasCompletedGuidedSetupFlow), which is exactly the "partially enabled / broken 2FA state" the bug description calls out for a new-domain account whose backend record says 2FA is required but the guided setup never completed.Now look at
useTwoFactorAuthRoute:https://github.com/Expensify/App/blob/main/src/hooks/useTwoFactorAuthRoute.ts#L21-L39When
requiresTwoFactorAuthis true, the resolver returnsSETTINGS_2FA_ENABLED→SCREENS.TWO_FACTOR_AUTH.ENABLED. But that screen is not inSET_UP_2FA_SCREENS, which is what gates the overlay-dismiss check:https://github.com/Expensify/App/blob/main/src/libs/Navigation/Navigation.ts#L70-L79So in the broken-state scenario the chain is:
twoFactorAuthSetupInProgress = trueandrequiresTwoFactorAuth = true→ overlay shows.getTwoFactorAuthRoute()returnsSETTINGS_2FA_ENABLEDbecauseis2FAEnabled = true.SET_UP_2FA_SCREENS,isIn2FASetupFlowstaysfalseand the absolute-fill overlay never un-mounts.It's not the underlying contradictory account state that breaks the button — the client-side flaw is that the overlay's own trigger condition admits a state where it routes to a screen that can't dismiss it.
What changes do you think we should make in order to solve the problem?
When
RequireTwoFactorAuthenticationOverlayis showing, the user — by the overlay's own definition — has not completed 2FA setup, so therequiresTwoFactorAuthshortcut in the resolver is the wrong branch for this caller. I'd let the resolver accept an explicit "I'm forcing setup" hint so the overlay's button always lands on a setup-flow screen that the overlay knows how to dismiss:type TwoFactorAuthRouteResult = { - getTwoFactorAuthRoute: (backTo?: Route) => Route; + getTwoFactorAuthRoute: (backTo?: Route, options?: {forceSetup?: boolean}) => Route; is2FAEnabled: boolean; }; function useTwoFactorAuthRoute(): TwoFactorAuthRouteResult { const [account] = useOnyx(ONYXKEYS.ACCOUNT); const is2FAEnabled = !!account?.requiresTwoFactorAuth; - const getTwoFactorAuthRoute = (backTo?: Route): Route => { - if (is2FAEnabled) { + const getTwoFactorAuthRoute = (backTo?: Route, options?: {forceSetup?: boolean}): Route => { + // Callers that force the user into setup (e.g. the RequireTwoFactorAuthenticationOverlay) + // must bypass the "already enabled" shortcut — the account can be in a partial state where + // `requiresTwoFactorAuth` is true but setup never completed (twoFactorAuthSetupInProgress). + if (is2FAEnabled && !options?.forceSetup) { return ROUTES.SETTINGS_2FA_ENABLED; } if (!account?.validated) { return createDynamicRoute(DYNAMIC_ROUTES.TWO_FACTOR_AUTH_VERIFY_ACCOUNT.path, backTo); } return createDynamicRoute(DYNAMIC_ROUTES.TWO_FACTOR_AUTH_ROOT.path, backTo); }; ... }Then in
RequireTwoFactorAuthenticationOverlay.tsx, pass the flag from the only caller that needs it:This keeps the existing 3-way resolver behavior for the other call sites (
SecuritySettingsPage,ConnectToXeroFlow,Enable2FACard,NonUSD/Finish) — they correctly want to land on the "enabled" page when 2FA is already on — and only the overlay opts into the unblocking behavior, where the destination is guaranteed to be inSET_UP_2FA_SCREENSso the overlay un-mounts.What alternative solutions did you explore? (Optional)
is2FAEnabledto require completed setup, e.g.!!requiresTwoFactorAuth && !needsTwoFactorAuthSetup && !twoFactorAuthSetupInProgress. Fixes the overlay path but also reroutesSecuritySettingsPageand the Xero/bank flows for any user briefly in mid-setup, which is a behavior change well outside this bug. Rejected.SCREENS.TWO_FACTOR_AUTH.ENABLEDtoSET_UP_2FA_SCREENSso the overlay dismisses when navigating to the enabled page. That makes the button feel responsive but lands the user on "2FA already enabled" while they've still failed to complete setup — wrong screen for the user's actual state. Rejected.RequireTwoFactorAuthenticationModal-style imperative open instead ofNavigation.navigate. Bigger refactor for the same outcome and doesn't address the underlying mis-routing in the resolver. Rejected.createDynamicRoute(...)insidehandleOnPresswithout touching the hook. Works, but duplicates theaccount?.validatedbranching that already lives inuseTwoFactorAuthRoute; the optional-flag approach keeps that logic in one place.KJ21-ENG commentedon May 28, 2026
Proposal
What is the root cause of that problem?
The reopened repro shows that
requiresTwoFactorAuthcannot be treated as proof that 2FA setup is finished.With this account state:
2FA is already required/enabled at the account level, but the user is still in the setup flow and still has incomplete NewDot onboarding. The client currently treats
requiresTwoFactorAuth: trueas the completed state in multiple 2FA routing paths:useTwoFactorAuthRoute()returns the static enabled route as soon asrequiresTwoFactorAuthis true.DynamicTwoFactorAuthPageredirects to the enabled page when it seesrequiresTwoFactorAuth.backTo, so dynamic 2FA routes can be built relative to the active onboarding route behind the overlay.That means the reviewer repro can show the required-2FA overlay, but pressing the CTA does not reliably open the active setup flow. It either targets the enabled page or gets pulled back into onboarding routing instead of continuing setup.
There is a second routing conflict while guided setup is incomplete. The onboarding router/guard still enforces onboarding as the active modal flow, so 2FA modal navigation can be treated as an attempt to leave onboarding. After setup succeeds, the Settings/Security success path also keeps the user in the settings 2FA flow instead of restoring the unfinished onboarding flow.
There is also a submit-time handoff issue after the user enters the 2FA verification code.
validateTwoFactorAuth()updates the auth token and callsopenApp()as soon as the API returns an auth token. In the required-2FA onboarding setup path, that unmounts the dynamic 2FA verify flow and lands the user on/homebefore the dynamic success page can cleartwoFactorAuthSetupInProgressand restart onboarding.What changes do you think we should make in order to solve the problem?
Treat
twoFactorAuthSetupInProgressas the source of truth for unfinished 2FA setup, even whenrequiresTwoFactorAuthis also true.Concretely:
needsTwoFactorAuthSetup && !requiresTwoFactorAuth, ortwoFactorAuthSetupInProgress && !hasCompletedGuidedSetupFlow.useTwoFactorAuthRoute()sorequiresTwoFactorAuth && twoFactorAuthSetupInProgressstill returns the dynamic setup/verify route instead ofSETTINGS_2FA_ENABLED.DynamicTwoFactorAuthPagewith the same rule, so it does not redirect in-progress setup users to the enabled page.ROUTES.SETTINGS_SECURITYwhen callinggetTwoFactorAuthRoute(), instead of deriving the dynamic route from the currently focused onboarding screen.isTwoFactorSetupScreen()helper that includes the 2FA right-modal parent route and 2FA setup/replacement leaf routes, then use it both for overlay hiding and onboarding guard checks.OnboardingGuardthat allows only required 2FA setup navigation while onboarding is incomplete. Unrelated non-onboarding navigation should still redirect back to onboarding.twoFactorAuthSetupInProgressis true and guided setup is incomplete, clear the 2FA setup progress and restart onboarding from the saved onboarding state instead of staying on the enabled settings page.validateTwoFactorAuth()succeeds: update the auth token, but skipopenApp()for this path. Then letDynamicVerifyPagenavigate to the success page only after the validation response clearstwoFactorAuthSecretKey, so the success page can perform the onboarding handoff.This keeps the fix frontend-only. It does not change the 2FA API contract, domain-policy requirements, or normal onboarding completion rules.
What alternative solutions did you explore? (Optional)
Only changing the overlay CTA route is not enough because
requiresTwoFactorAuth: truewould still makeuseTwoFactorAuthRoute()andDynamicTwoFactorAuthPagechoose the enabled page while setup is still in progress.Only changing
OnboardingGuardis not enough because the app would still classify the reviewer repro as completed 2FA setup and skip the setup screen.Only hiding the overlay during 2FA screens is also too narrow because it does not solve the route selection problem or the required return to onboarding after setup success.
melvin-bot commentedon May 28, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cretadn22 (
External)wildan-m commentedon May 28, 2026
🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.
[-]Required 2FA setup screen is unresponsive, blocking new-domain login and account merge[/-][+][$250] Required 2FA setup screen is unresponsive, blocking new-domain login and account merge[/+]melvin-bot commentedon May 28, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022060024083406042078
github-actions commentedon May 28, 2026
141 remaining items
thelullabyy commentedon Oct 15, 2026
Price increase request
Mandatory
Proposed amount: $625 total: $375 for #94486 and $250 for #100077.
Why the work exceeded the issue: The issue asked to unblock the Enable 2FA button, but the implementation required coordinating 2FA routing, onboarding guards, verification, and the return to onboarding after setup. Review also added a Sign out / Leave account option beyond the original expected behavior, delivered in a separate PR with shared sign-out logic and unit tests.
Regressions caused by this PR:
Optional
Scope expansion: The Sign out option was discussed during review and deferred so the original fix could ship sooner. Product subsequently confirmed that the follow-up should remain under this issue. It required handling offline confirmation, active GPS trips, unsaved receipts, copilot Leave account behavior, and repeated presses.
Files touched:
Core flow changes: Required 2FA during incomplete onboarding, including verification → success → onboarding resume; and sign-out / leaving a delegated account from the blocking overlay. These changes touch authentication, navigation, and safeguards for unsaved data.
Test coverage: The PRs document testing across Android native, Android Chrome, iOS native, iOS Safari, and desktop Chrome/Safari. Coverage includes completing required 2FA and resuming onboarding, normal Settings 2FA, overlay sign-out, and offline behavior. Full onboarding passes required fresh accounts; automated coverage includes navigation guards, onboarding, session actions, 2FA routing, and the shared sign-out hook.
Multiple PRs:
mallenexpensify commentedon Oct 16, 2026
@iwiznia 👀 on the price increase above plz. I have a Clause project for reviews, they returned the below. _They'_re often a bit stringent when it comes to regressions
neerajbachani commentedon Oct 17, 2026
@mallenexpensify Thanks for reviewing this. I would like to add a few points.
#100077 as new scope: Agreed. Sign out is not part of the original issue. @joekaufmanexpensify asked for it as a follow-up after we moved it out of #94486 so the first fix could ship sooner.
On the #94486 regression: The line that caused #98938 and #98933 came from my merge commit 3401261. While resolving a conflict in
DynamicSuccessPage, I passedfalseinstead of the realhasCompletedGuidedSetupFlow. It was one condition, so both reports had one cause and one fix, #98940, and @thelullabyy counted it as one regression.When the blockers came up, I joined the #expensify-open-source thread the same night. I reviewed MelvinBot's fix and confirmed it matched the fix I had found, with a recording: https://expensify.slack.com/archives/C01GTK53T8Q/p1787165068610639?thread_ts=1787106700.721209&cid=C01GTK53T8Q. @thelullabyy asked me to help test #98933, so I tested it and confirmed that Got it keeps the user on Security with the 2FA page open, which is the expected result. #98940 shipped the next day.
On testing: Each full pass of #94486 needed a new account, because onboarding shows only on the first login. It also needed a domain that requires 2FA, and the full 2FA setup each time: verify, save the recovery codes, enter the authenticator code, and return to onboarding. This path needed a real domain account, which is why review moved to @thelullabyy. #100077 needed the same domain setup to reach the overlay, plus the copilot, GPS trip, unsaved receipt, and offline cases.
So I would still like to request $625: $375 for #94486 and $250 for #100077. If the regression rule needs to apply, I would ask that the help with the fix and the retest be considered against the 50% reduction, so that #94486 stays at $250.
Thank you!
cc: @iwiznia
iwiznia commentedon Oct 20, 2026
Agree that #100077 is new scope and to value that at $250, but I am not convinced of the increase for #94486 mainly because it was in scope and even if it was more work, it indeed caused a regression, so I think that kind of evens out. My recommendation would be $500 in total, what do you guys think?
mallenexpensify commentedon Oct 20, 2026
Payment Summary
Contributor: @neerajbachani paid $500 via Upwork
Contributor+: @thelullabyy due $500 via NewDot
@neerajbachani can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022112601723473331661
You can discuss the price still too, I can raise easily, if we decide to
neerajbachani commentedon Oct 20, 2026
@mallenexpensify I've accepted the job offer, thanks!!
melvin-bot commentedon Oct 20, 2026
@thelullabyy Eep! 4 days overdue now. Issues have feelings too...
mallenexpensify commentedon Oct 21, 2026
@neerajbachani paid, summary updated above. Thx.
melvin-bot commentedon Oct 22, 2026
@thelullabyy Still overdue 6 days?! Let's take care of this!
laurenreidexpensify commentedon Oct 27, 2026
$500 Approved @thelullabyy New Expensify
Krishna2323 commentedon Nov 13, 2026
Heads up: the fix for this issue (#94486) caused a regression. Admins who had finished onboarding stayed on Account > Security after completing the required 2FA setup, instead of landing on Home. Tracked in #101848 and fixed in #102482.