[$250] VBA - Continue modal is not shown after several attempts

[lanitochka17]

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.0.46-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #49687

Action Performed:

Precondition: user has several workspaces, e.g. A, B, C

1. Go to workspace A > More features > enable Expensify Cards
2. Go to Expensify Cards tab > issue new card
3. Start add VBA flow
4. Close VBA flow RHN on Personal info step
5. Go to workspace B > More features > enable Expensify Cards
6. Go to Expensify Cards tab (ws B) > issue new card
7. Repeat step 2-6 several times

Expected Result:

On step 5, starting page of VBA with setup types displayed
On step 6, Continue page with options 'Continue' and 'Start over' displayed

Actual Result:

On step 5, starting page of VBA with setup types displayed
On step 6, after several attempts, user is navigated to Personal info step he left on step 4

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

Bug6628321_1728391481784.vba_fail.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021843708220772796908
• Upwork Job ID: 1843708220772796908
• Last Price Increase: 2024-10-08
• Automatic offers:
• DylanDylann | Contributor | 104330185

Issue Owner

Current Issue Owner: @koko57

[melvin-bot]

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

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

[marcochavezf]

Seems this issue stems from this PR. Given that PR fixed a crash and this workflow is not common, I wouldn't consider it a deploy blocker, but it would still require a fix cc @koko57 @mountiny @grgia @DylanDylann Feel free to take it over since you have more context than I do :)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021843708220772796908