[HOLD for payment 2023-11-22] [HOLD for payment 2023-11-21] Workspace - Start over page is not shown when user quits bank account setup and revisits it

[kbecciv]

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: 1.3.98.0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Navigate to staging.new.expensify.com
2. Go to Settings > Workspaces > any workspace.
3. Click Bank account.
4. Click Connect manually.
5. Proceed until Step 3 of bank account setup.
6. Close the setup by clicking outside the RHN.
7. Go to Settings > Workspaces > any workspace.
8. Click Bank account.

Expected Result:

User will be presented with 'Continue with setup' and 'Start over' screen.

Actual Result:

User is redirected to where the bank account setup is left off.
In order to see 'Continue with setup' and 'Start over' screen, user has to return to the first screen.
On PROD, user is presented with 'Continue with setup' and 'Start over' screen after closing the setup and revisiting bank account page.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6271756_1699647092519.20231111_024250__1_.mp4

View all open jobs on GitHub

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @johnmlee101 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[johnmlee101]

#29166 might be related

[johnmlee101]

Asked in deployer for some extra 👀

[johnmlee101]

Reverted it locally and it fixes it, so marking it as a regression