[$250] [Due for payment 2025-08-22] Sign in page text not displayed correctly after switching experiences

[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 occur when you sign in and land in classic, only when you sign in and land in NewDot, then perform the steps... so I'm not marking this a blocker

Action Performed:

• Make sure your account is set to NewDot experience
• Sign in to NewDot in HybridApp
• Switch to classic with Account > Switch to...
• In classic navigate to settings
• Sign out

Expected Result:

• At the NewDot sign-in page the text should display correctly

Actual Result:

• The text doesn't display correctly, you see the string names such as common.continue

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

Signoutofclassic-strings.mp4

Issue Owner

Current Issue Owner: @trjExpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021957474062469550991
• Upwork Job ID: 1957474062469550991
• Last Price Increase: 2025-08-18

[melvin-bot]

Triggered auto assignment to @trjExpensify (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]

Known to me and Marcin. We're about to revert the signin page so this likely won't be shipped for a while

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.