Android - Expensify Classic opens after relaunching when New Expensify is last opened

[lanitochka17]

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.0.63-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+zm51@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Launch hybrid app
2. Sign in
3. If app lands on Expensify Classic, go to Menu > Try New Expensify
4. If app lands on New Expensify, go to Settings > Switch to Expensify Classic
5. On Expensify Classic, open Menu > Try New Expensify to go back to New Expensify
6. Kill app
7. Relaunch app

Expected Result:

New Expensify will open on hybrid app after relaunching app because New Expensify is the last opened section

Actual Result:

Expensify Classic opens on hybrid app after relaunching app when New Expensify is the last opened section

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6666751_1731706307198.Bug6666735_1731706154822_Screen_Recording_20241116_052851.1.mp4

Add any screenshot/video evidence

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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.

[melvin-bot]

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

[melvin-bot]

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

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

[arosiclair]

Working on getting access to the Android beta for OldApp

[arosiclair]

Okay I reproduced in v9.0.63-3

[arosiclair]

Looks like the root of this problem is that opening the new experience does not update tryNewDot.classicRedirect.dismissed to false. I'm not sure why yet.

[arosiclair]

Okay we already merged a PR to fix it! This was caused by mixed up params that skipped updating the tryNewDot NVP from https://github.com/Expensify/Mobile-Expensify/pull/13257 and should be fixed with https://github.com/Expensify/Mobile-Expensify/pull/13286.