[Due for payment 2026-05-18] [Due for payment 2026-04-23] [Due for payment 2026-04-20] Initial page shows log in/connect button instead of Continue setup for partially set up bank

[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.58-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #86645
Email or phone of affected tester (no customers): applausetester+sjois2jd@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• User has a partially set up bank account in the workspace.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Workflows.
3. Click on the partially set up bank account.
4. Click Continue setup.
5. Click RHP back button until it returns to initial screen.

Expected Result:

Continue setup and Start over button will be shown on the initial screen because bank is partially set up.

Actual Result:

Log into your bank and Connect manually button are shown on the initial screen when bank is partially set up.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7126624_1775817123326.6.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dukenv0307

[melvin-bot]

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

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

[MelvinBot]

Proposal

What is the root cause of that problem?

PR #86645 refactored the USD bank account flow into a separate page (USDVerifiedBankAccountFlowPage). The entry point decides which buttons to show based on shouldShowContinueSetupButton state in ReimbursementAccountPage.

When the user clicks "Continue setup", continueUSDVBBASetup sets shouldShowContinueSetupButton = false before navigating to the USD flow. Previously, the goBack handler in ReimbursementAccountPage restored this flag to true when backing out of the COUNTRY step. After the refactor, the back button on the Country page is handled by USDVerifiedBankAccountFlowPage.onBackButtonPress, which calls Navigation.goBack() directly — bypassing the old goBack handler entirely.

The sync effect that calls setShouldShowContinueSetupButton(shouldShowContinueSetupButtonValue) doesn't re-fire on back navigation because none of its dependencies (achData, shouldShowContinueSetupButtonValue, etc.) changed while the user was in the USD flow.

What changes do you think we should make in order to solve the problem?

Add screen focus awareness to ReimbursementAccountPage so that shouldShowContinueSetupButton is re-synced when the page regains focus after navigating back from the USD flow. Use React Navigation's useIsFocused hook: when the screen becomes focused again, re-set shouldShowContinueSetupButton to shouldShowContinueSetupButtonValue (which correctly reflects the in-progress state from achData).

This approach is more robust than patching the back handler in USDVerifiedBankAccountFlowPage because it handles all navigation paths back to the entry point (back button, gesture, deep link, etc.).

What alternative solutions did you explore? (Optional)

1. Patch USDVerifiedBankAccountFlowPage.onBackButtonPress to reset shouldShowContinueSetupButton before calling Navigation.goBack(). This would work but is fragile — any other navigation path back to the entry point (e.g., Android back gesture, deep link) would still have the bug.
2. Remove setShouldShowContinueSetupButton(false) from continueUSDVBBASetup and instead determine the button state from the route/navigation state. This is cleaner long-term but a larger change.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[koko57]

looking into it

[arosiclair]

Continue setup and Start over button will be shown on the initial screen because bank is partially set up.

I suppose this would be ideal, but navigating all the way back just to use the continue or start over options seems very rare/weird. I'll demote this.