Redirect back to wallet after account successfully added by koko57 · Pull Request #82621 · Expensify/App

koko57 · 2026-02-17T08:20:41Z

Explanation of Change

Fixed Issues

$ #82610
PROPOSAL: -

Tests

Prerequisites: at least one workspace (owned)

Go to Wallet page and click Add bank account
Click on Get reimbursed
Select any non-usd country and click Next
Fill in the form (any steps required)
On the confirmation page Accept the terms and Confirm
Verify that you see the success page
Click Continue
Verify that you're redirected back to Wallet page

Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

Screen.Recording.2026-02-17.at.09.36.29.mp4

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-02-17.at.09.10.08.mp4

codecov · 2026-02-17T08:27:23Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
...ositAccount/InternationalDepositAccountContent.tsx	`0.00% <0.00%> (ø)`
... and 11 files with indirect coverage changes

koko57 · 2026-02-17T08:58:08Z

I have some problems with recordings of other platforms, but I don't want to block the PR for that

melvin-bot · 2026-02-17T08:58:19Z

@dominictb Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

github-actions · 2026-02-17T09:01:39Z

PR Review

Change: Single-line modification in InternationalDepositAccountContent.tsx that skips backTo navigation when backTo contains ROUTES.SETTINGS_BANK_ACCOUNT_PURPOSE, falling through to the switch that routes to SETTINGS_WALLET.

Suggestions

Use strict equality instead of includes (InternationalDepositAccountContent.tsx:85) — backTo.includes() is a substring match that could unintentionally match longer routes. Since backTo is typed as Route, strict equality (!==) is more precise.
Consider fixing at the source — The root cause is BankAccountPurposePage/substeps/CountrySelection.tsx:66 passing itself as backTo. Passing ROUTES.SETTINGS_WALLET or omitting backTo entirely would avoid adding route-specific exclusions in the destination component.

Neither suggestion is blocking — the current fix works correctly for the reported issue.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2964a9be8b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-02-17T09:06:08Z

src/pages/settings/Wallet/InternationalDepositAccount/InternationalDepositAccountContent.tsx

+        if (backTo && !backTo.includes(ROUTES.SETTINGS_BANK_ACCOUNT_PURPOSE)) {
            Navigation.goBack(backTo);


Scope bank-account-purpose bypass to success exit only

This condition now skips Navigation.goBack(backTo) whenever backTo points to SETTINGS_BANK_ACCOUNT_PURPOSE, but goBack() is also used by handleBackButtonPress on the first substep (country selector), not just on success. In that flow, pressing back/cancel now sends users to Wallet instead of returning to the purpose screen they came from, so they lose the ability to back out and choose a different purpose without restarting the flow.

Useful? React with 👍 / 👎.

It's intentional

and strict equality doesn't work here as backTo param gets additional / at the beginning, ROUTE doesn't include /

situchan · 2026-02-17T10:35:05Z

If this requires C+ review, I can help as @dominictb's moved to backend team

joekaufmanexpensify · 2026-02-17T10:58:40Z

This is related to an existing project @dominictb is finishing up before fully offboarding to backend

github-actions · 2026-02-17T12:38:17Z

🚧 @joekaufmanexpensify has triggered a test Expensify/App build. You can view the workflow run here.

dominictb · 2026-02-17T17:03:23Z

The changes in the PR would mean we couldn't go back to the purpose page in personal bank account flow:

Screen.Recording.2026-02-18.at.00.02.15.mov

That is inconsistent with BBA flow.

joekaufmanexpensify · 2026-02-17T18:07:37Z

Hm, yeah that should work the same way for both. Navigating back from the country list should drop you on the purpose page.

koko57 · 2026-02-18T07:53:26Z

@dominictb @joekaufmanexpensify fixed

github-actions · 2026-02-18T08:48:27Z

🚧 @joekaufmanexpensify has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-02-18T08:52:35Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #82621.

Android 🤖	iOS 🍎
⏩ SKIPPED ⏩	⏩ SKIPPED ⏩
The build for Android was skipped	The build for iOS was skipped

Web 🕸️
https://82621.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

dominictb · 2026-02-18T09:28:47Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-02-18.at.16.32.24.mov

dominictb

🎀

joekaufmanexpensify

Works well from a product perspective 👍

joekaufmanexpensify · 2026-02-18T12:29:56Z

all yours @srikarparsi

OSBotify · 2026-02-18T19:01:15Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2026-02-18T19:11:05Z

🚧 @srikarparsi has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-02-18T19:15:10Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #82621.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-cb58d68-a53e5e7-fd5ad908fd3afa9023fdd959e261483bd1d8279e/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-cb58d68-a53e5e7-4960437479a7c00292230144e4a02a2b2bcc51aa/index.html

Web 🕸️
https://82621.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-18T22:21:35Z

🚀 Deployed to staging by https://github.com/srikarparsi in version: 9.3.22-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

OSBotify · 2026-02-19T17:22:24Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.22-4 🚀

platform	result
🕸 web 🕸	cancelled 🔪
🤖 android 🤖	success ✅
🍎 iOS 🍎	cancelled 🔪

OSBotify · 2026-02-19T17:36:44Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.22-4 🚀

platform	result
🕸 web 🕸	failure ❌
🤖 android 🤖	success ✅
🍎 iOS 🍎	cancelled 🔪

fix: redirect back to wallet after account successfully added

2964a9b

melvin-bot bot assigned koko57 Feb 17, 2026

koko57 marked this pull request as ready for review February 17, 2026 08:58

koko57 requested review from a team as code owners February 17, 2026 08:58

melvin-bot bot requested review from dominictb and joekaufmanexpensify and removed request for a team February 17, 2026 08:58

melvin-bot bot removed the request for review from a team February 17, 2026 08:58

koko57 mentioned this pull request Feb 17, 2026

Wallet - User back to select the type of bank account after adding one #82610

Closed

7 tasks

chatgpt-codex-connector bot reviewed Feb 17, 2026

View reviewed changes

This comment has been minimized.

Sign in to view

koko57 added 3 commits February 18, 2026 08:36

Merge branch 'main' into fix/82610-redirect-back-to-wallet

4bccb9e

fix: navigation fix

ae61b17

fix: minor fix

120c0b3

dominictb approved these changes Feb 18, 2026

View reviewed changes

melvin-bot bot requested a review from srikarparsi February 18, 2026 09:33

joekaufmanexpensify approved these changes Feb 18, 2026

View reviewed changes

srikarparsi merged commit cb58d68 into Expensify:main Feb 18, 2026
30 checks passed

OSBotify mentioned this pull request Feb 18, 2026

Deploy Checklist: New Expensify 2026-02-18 #82863

Closed

76 tasks

		if (backTo && !backTo.includes(ROUTES.SETTINGS_BANK_ACCOUNT_PURPOSE)) {
		Navigation.goBack(backTo);

Conversation

koko57 commented Feb 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov bot commented Feb 17, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

koko57 commented Feb 17, 2026

Uh oh!

melvin-bot bot commented Feb 17, 2026

Uh oh!

github-actions bot commented Feb 17, 2026

PR Review

Suggestions

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Feb 17, 2026

Choose a reason for hiding this comment

Uh oh!

koko57 Feb 17, 2026

Choose a reason for hiding this comment

Uh oh!

koko57 Feb 17, 2026

Choose a reason for hiding this comment

Uh oh!

situchan commented Feb 17, 2026

Uh oh!

joekaufmanexpensify commented Feb 17, 2026

Uh oh!

github-actions bot commented Feb 17, 2026

Uh oh!

This comment has been minimized.

dominictb commented Feb 17, 2026

Uh oh!

joekaufmanexpensify commented Feb 17, 2026

Uh oh!

koko57 commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

Uh oh!

dominictb commented Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

dominictb left a comment

Choose a reason for hiding this comment

Uh oh!

joekaufmanexpensify left a comment

Choose a reason for hiding this comment

Uh oh!

joekaufmanexpensify commented Feb 18, 2026

Uh oh!

Uh oh!

OSBotify commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

Uh oh!

OSBotify commented Feb 18, 2026

Uh oh!

OSBotify commented Feb 19, 2026

Uh oh!

OSBotify commented Feb 19, 2026

Uh oh!

Reviewers

koko57 commented Feb 17, 2026 •

edited

Loading

codecov bot commented Feb 17, 2026 •

edited by github-actions bot

Loading

dominictb commented Feb 18, 2026 •

edited

Loading