[Due for payment 2025-08-15] [RCA #65178] Stuck after signing out of classic on HybridApp

[Julesssss]

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.1.89-1
Reproducible in staging?: Yes
Reproducible in production?: No

This doesn't seem to occur when you sign in and land in classic, only when you sign in and land in NewDot, then perform the steps...

Action Performed:

• Sign in to NewDot in HybridApp
• Switch to classic with Account > Switch to...
• In classic navigate to settings
• Sign out

Expected Result:

• You should be signed out and land at the NewDot sign in page
• You should be able to sign back in
• It is known that the text won't show correctly

Actual Result:

• Sometimes you get stuck with a spinner and the strings haven't loaded correctly

Workaround:

Kill app and open again, it works fine

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
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

AndroidClassicSignout.mp4

Issue Owner

Current Issue Owner: @strepanier03

[melvin-bot]

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

[Julesssss]

Hey @war-in. FYI I noticed this while testing this issue. If you could take a look tomorrow that would be great, thanks.

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