Wallet-Undefined currency loading page and error is shown while adding personal bank account.

[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: V9.3.62-6
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #86993
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: Redmi note 10s android 13
App Component: User Settings

Action Performed:

1. Launch app
2. Open wallet - add bank account - get reimbursed
3. Select hongkong and try to complete the flow
4. Tap continue on personal bank account page added
5. Note confirm button shown in middle of page
6. After few seconds , tap currency field shown as undefined
7. Note page loads infinitely
8. Navigate back and tap confirm
9. Note page shows error
10. Navigate back and note all bank account steps are shown
11. In wallet page note account is added

Expected Result:

Personal bank account must be added without error.

Actual Result:

Undefined currency loading page and error is shown while adding personal bank account.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7139439_1777309939235.Screenrecorder-2026-04-27-22-33-58-304.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @apeyada

[melvin-bot]

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

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