[Due for payment 2026-03-19] [GPS] iOS - Unit is shown in different language on notification panel and dynamic island

[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.33-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #83592
Email or phone of affected tester (no customers): sdosidjiosdjnojsio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 Pro Max / iOS 26.3
App Component: Money Requests

Action Performed:

Precondition:

• Device has dynamic island.
• App language is Chinese or Japanese.
• User is tracking GPS distance.

1. Background Expensify app.
2. Pull down notification panel.
3. Close notification panel

Expected Result:

Live activity on notification panel and dynamic island will show the unit in same language.

Actual Result:

Live activity on notification panel shows unit in Chinese.
Live activity on dynamic island shows unit in English.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @GCyganek

[melvin-bot]

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

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