[Due for payment 2026-08-10] Bank Account- Select a State navigate back to previous page of Company info

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.48-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: https://test-management.browserstack.com/projects/2219752/test-runs/67224479/folder/13176694/41236762/1622117220
Email or phone of affected tester (no customers): duytestnguyen+326@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 11 Home/Chrome
App Component: Workspace Settings

Action Performed:

Preconditions:

• Create new account and validate
• Create new workspace

1. Open https://staging.new.expensify.com/
2. Navigate to Workflows on workspace settings
3. Start add bank account with Plaid
4. Follow the flow till 'What's your company’s incorporation date?'
5. Select a date and click 'Next'
6. Select a State

Expected Result:

User stays in Which state was your company incorporated in? page and can click 'Next'

Actual Result:

User navigates back to 'What's your company’s incorporation date?' page. Unable to continue

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7223303_1785572690950.Adfadf_s_Workspace_-_Workflows_-_Google_Chrome_2026-08-01_15-13-54.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7223303

Issue Owner

Current Issue Owner: @suneox

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/50181018dc183ddee631f502eeadc5a50f4cf746c6b26f01d69f1eacb7a09f30

[melvin-bot]

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

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

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #97072 - "83361 setting profile part 1" by @huult (High confidence)
Related Issues: None

Recommendation: REVERT

PR #97072 migrated the shared StateSelector to the new dynamic-route system, but its QA steps only covered the Settings/Profile address flow — it did not test the VBA (add bank account) Business Info "incorporation state" step, which also uses StateSelector and is now driven by URL-based sub-page navigation. The safest immediate action is to revert; a targeted fix is also viable (see below).

Assigned: @huult (PR author), @mjasikowski, @suneox (approving reviewers) from the causing PR
Labels: No change. Kept DeployBlockerCash (Frontend bug, blocks the App deploy). DeployBlocker was not present, so nothing to remove.

📋 Detailed Analysis

Evidence

• Bug reproduces on staging (9.4.48-0) but not production, so it is a regression introduced by a PR in this release.
• Of all files in this release's production...staging diff, the only shared component in the affected flow that changed is src/components/StateSelector.tsx.
• git/GitHub history shows the two commits that touched StateSelector.tsx in this release — migrate ADDRESS_STATE and migrate ADD_DEBIT_CARD — both belong to PR 83361 setting profile part 1 #97072 (gh api repos/Expensify/App/commits/<sha>/pulls).
• PR 83361 setting profile part 1 #97072's QA steps only cover SETTINGS_ADDRESS_STATE (profile address) and SETTINGS_CONTACT_METHODS. The ReimbursementAccount / VBA Business Info incorporation-state step was not tested, yet it renders the same StateSelector.

What changed in PR #97072 (the state selector navigation)

Before, the selector navigated to a dedicated modal route and explicitly passed the current active route as the back target:

const activeRoute = Navigation.getActiveRoute();
Navigation.navigate(stateSelectorRoute.getRoute(stateCode, activeRoute, label));

After, it appends a dynamic state suffix onto the current route and no longer passes an explicit back target:

Navigation.navigate(createDynamicRoute(DYNAMIC_ROUTES.ADDRESS_STATE.getRoute(stateCode, label)));

The stateSelectorRoute prop (which previously let callers control the exact return route) was also removed.

Verification

Affected files (all in Expensify/App at HEAD 4ff4738a4d1b7e961c5ab31336a2d8304d8f5999):

• src/components/StateSelector.tsx — changed by 83361 setting profile part 1 #97072; used by the incorporation-state step.
• src/pages/ReimbursementAccount/USD/BusinessInfo/subSteps/IncorporationStateBusiness.tsx — renders <StateSelector>.
• src/pages/ReimbursementAccount/USD/BusinessInfo/BusinessInfo.tsx — the Business Info flow is URL-based via useSubPage, keeping the current sub-step in the subPage URL param.
• src/hooks/useSubPage/index.tsx — when subPage (urlPageName) is absent it sets isRedirecting and redirects to startFrom = getInitialSubStepForBusinessInfo(values).
• src/pages/ReimbursementAccount/USD/utils/getInitialSubStepForBusinessInfo.ts — returns index 6 (the incorporation DATE page) whenever the incorporation values don't yet include a saved state/date.

Root Cause

The Business Info flow now stores the active sub-step in the subPage URL param and relies on it for navigation. The old state selector pushed a dedicated modal on top of the Reimbursement Account screen and passed the exact active route as backTo, so dismissing it returned to the screen with subPage=incorporationState intact.

After #97072's migration, the state selector is a dynamic-route suffix on the same screen with no explicit back target. Returning from state selection no longer preserves the subPage=incorporationState context. With urlPageName gone, useSubPage treats the screen as needing a redirect and sends the user to getInitialSubStepForBusinessInfo(...), which — because the incorporation state (and/or date) isn't yet persisted in the computed values — resolves to the incorporation DATE sub-step. Net effect: selecting a state bounces the user back to "What's your company's incorporation date?" and they cannot proceed.

Fix options

1. REVERT 83361 setting profile part 1 #97072 (default, safest for the deploy).
2. Targeted fix: preserve the sub-step context when returning from the dynamic state route (e.g., restore an explicit back target / subPage param), or exclude the ReimbursementAccount Business Info flow from the dynamic ADDRESS_STATE migration until the URL-based sub-page flow is handled.