[Due for payment 2026-08-27] [$250] Security - "What's your work email?" window appears briefly after setting up 2FA

[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.56-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: #98756
Email or phone of affected tester (no customers): fischer9966+081826+98519@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 17 Pro / 26.6. Google Pixel 5 / Android 14
App Component: User Settings

Action Performed:

1. Open Expensify app on iOS or Android
2. Login with Gmail account
3. Go to Account > Security > Two Factor Authentication (2FA)
4. Tap to "Download codes"
5. Enter the 6 digit code from the authenticator app
6. Tap "Next"
7. Tap "Got it" on confirmation screen

Expected Result:

The user proceeds to the next screen without the appearance of elements unrelated to the flow.

Actual Result:

After setting up 2FA user proceeds to the next screen after which "What's your work email?" window appears briefly.
Sometimes a screen "Whats your name" may appear instead of "What's your work email?"

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7236811_1787106141715.Android-Whats-your-name-screen-after-2FA.mp4

Bug7236811_1787103005628.98519-iOS.mp4

Bug7236811_1787103005619.98519-Android.mp4

View all open jobs on GitHub

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

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022090160402810620327
• Upwork Job ID: 2090160402810620327
• Last Price Increase: 2026-08-19

Issue Owner

Current Issue Owner: @linhvovan29546

[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/e9dc52e20b1666d1db6197b15edaf3e99c88c121be083e463ffceebdac65c747

https://platform.applause.com/services/links/v1/external/964dffe90a5add1e142c2e05edd9a4180a186e598e9cfa17f046218387fe433f

https://platform.applause.com/services/links/v1/external/ec4126fbbd714e635d648ee43a81d25b98df0712f3eecbda645ed1897b4a854f

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #98756

[melvin-bot]

@roryabraham @linhvovan29546 you have been assigned to this deploy blocker because you reviewed the offending PR: #98756

[melvin-bot]

@jakubstec you have been assigned to this deploy blocker because you authored the offending PR: #98756

[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