[Due for payment 2026-06-16] [Due for payment 2026-06-02] Account-Country return to geolocation when back from magic code page

[applause-bot]

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: v9.3.81-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91000
Email or phone of affected tester (no customers): sintayewhaylu01+s1135@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: web
App Component: Workspace Settings

Action Performed:

1. Navigate to staging.new.expensify.com
2. Go to Account > Profile.
3. Click Address.
4. Notice Country field is auto-populated with your geolocation-derived country (when no address is saved).
5. Enter an address on Address line 1.
6. Tap a suggestion
7. Notice Address line 1, City, State, ZIP/Post Code, and Country are filled in.
8. Tap Save and when magic code page open tap back button

Expected Result:

The country should not be back to geolocational country but keep the filled one in step 6.

Actual Result:

Country returned to geoloaction country

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7162693_1779714236665.bandicam_2026-05-25_15-51-18-879.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7162693

[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/943f1ebc640217d94756fa1dc7c4c46e61af5cc255a21676b91abce3701a82a2

[melvin-bot]

@rafecolton recently merged #91000, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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

[mjasikowski]

@MelvinBot diagnose the root cause, propose a fix

[mountiny]

I have raised a revert of the PR, waiting some time until QA does more testing so we catch as many issues in the flow as possible