Android - Onboarding - Test drive modal appears twice, tab is not responsive

[mitarachim]

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: 9.3.11-49
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80965
Email or phone of affected tester (no customers): hsshzjkssksksksksk@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Other

Action Performed:

Precondition:

• Fresh install the app.

1. Launch Expensify app.
2. Create a new account.
3. Tap Skip on work email step.
4. Select Track and budget expenses.
5. Complete the onboarding.
6. Tap Skip on test drive modal.
7. Tap Skip again on test drive modal.
8. Go to Workspaces > Account > Workspaces > Inbox.
9. Switch between different tabs.

Expected Result:

• Test drive modal will appear once.
• Tab will be responsive after skipping test drive modal and switching tab.

Actual Result:

• Test drive modal appears twice.
• Tab is not responsive after skipping test drive modal and switching tab.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7067409_1770239596837.Screen_Recording_20260205_050906_Expensify.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @kadiealexander (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

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