Wallet - Selected account type is not shown after returning back

[IuliiaHerets]

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.0.80-2
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 TestRail: #52322
Email or phone of affected tester (no customers): dave0123seife@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 14.5/ Chrome
App Component: User Settings

Action Performed:

1. Login to NewDot.
2. Go to Settings > Wallet > Add bank account.
3. Click Add bank account.
4. Select any county other than United States(or select India)
5. Click Next.
6. Enter Valid Account number and IFSC > Next
7. Select Account type
8. Go back by clicking < button
9. Click Next button to return to Account type selector page

Expected Result:

You land on the account type selector with your prior selection shown.

Actual Result:

User lands on the account type selector with no prior selection shown.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6704938_1735792011902.Screen_Recording_2025-01-02_at_7.14.42_in_the_morning.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @shubham1206agra

[melvin-bot]

Triggered auto assignment to @nkuoch (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

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

[Beamanator]

@nkuoch in slack - https://expensify.slack.com/archives/C01GTK53T8Q/p1735808219476769?thread_ts=1735807953.968909&cid=C01GTK53T8Q - @shubham1206agra mentioned this is expected, so I'm at least marking this NAB - feel free to close it out, but i was planning to wait for @MonilBhavsar to confirm

[sakluger]

@MonilBhavsar please close out the issue if this is expected. Thanks!

[MonilBhavsar]

We agreed that we need to fix this

[sakluger]

@shubham1206agra says that this is a polish issue that is already being kept track of in another issue. Closing!