[Due for payment 2026-08-19] Wallet - Back button and Continue on "Personal bank account added!" screen reopen the add bank account flow instead of returning to Wallet

[sharabai]

Version Number: 9.4.46-4
Reproducible in staging?: Y
Reproducible in production?: N/A
If this was caught during regression testing, add the test name, ID and link from BrowserStack: N/A
Email or phone of affected tester (no customers): N/A
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: N/A
Issue reported by: @sharabai
Slack conversation (hyperlinked to channel name): N/A

Action Performed:

1. Go to Account > Wallet (/settings/wallet)
2. In the "Bank accounts" section, click "Add bank account"
3. On the "Where's your bank account located?" page, keep United States selected and click Next
4. On the "Streamline payments" entry point, choose "Log into your bank" and complete the Plaid sandbox flow (e.g. Wells Fargo > Plaid Saving)
5. Complete the remaining steps of the flow (address, confirmation) and submit
6. The "Personal bank account added!" success screen is shown at /settings/wallet/add-us-bank-account
7. Click the back arrow in the RHP header (or the "Continue" button)

Expected Result:

The RHP flow is dismissed and the user is returned to the Wallet page (/settings/wallet), since the bank account was already added successfully.

Actual Result:

The app navigates back into the already-completed add bank account flow: first to the "Streamline payments" entry point (/settings/wallet/add-us-bank-account/entry-point), and pressing back again shows the country selection page (/settings/wallet/add-bank-account/country?backTo=%2Fsettings%2Fwallet) before finally reaching Wallet. The same wrong navigation happens when clicking the "Continue" button on the success screen.

Workaround:

Yes — the bank account is added correctly; the user can keep pressing back through the stale flow screens or navigate to Wallet manually.

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

Screenshots/Videos

Navigation.back.mp4

View all open jobs on GitHub

[Manohar2503]

Hi I would like to work on this issue if it's available. I'll investigate the root cause and submit a PR with a fix. Please let me know if someone is already working on it. Thanks.

[melvin-bot]

📣 @Manohar2503! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[Manohar2503]

Contributor details

Expensify account email: manujinka22@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~0196bd4a9c94220df9

[melvin-bot]

Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

10 days overdue. Is anyone even seeing these? Hello?

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.52-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Add a Time sensitive to-do for employees with missing deposit accounts #96623

If no regressions arise, payment will be issued on 2026-08-19. 🎊

The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

[melvin-bot]

12 days overdue now... This issue's end is nigh!

[sharabai]

@MelvinBot the issue should be resolved with the PR merged