[HOLD for payment 2024-05-02] CRITICAL: [Actionable Whispers] [$500] Unable to return to invite page after returning to confirmation page

[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.4.63-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #38709
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to FAB > Track expense.
3. Create a track scan expense.
4. From the whisper, select Share it with my accountant.
5. Select a workspace > Click Submit.
6. Click back button on the Invite member RHP.
7. Click Submit.
8. Click back button twice.

Expected Result:

In Step 7, user should be able to submit the expense, or user should be at least allowed to proceed to invite member page.
In Step 8. the RHP will close after clicking on the back button twice.

Actual Result:

In Step 7, user is unable to proceed to invite member page after clicking on the Submit button.
In Step 8. not here RHP shows up.

Workaround:

n/a

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

Bug6453802_1713455097071.bandicam_2024-04-18_23-38-24-015.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~019390c3acf2a50745
• Upwork Job ID: 1781106052824424448
• Last Price Increase: 2024-04-19
• Automatic offers:
• jjcoffee | Reviewer | 0
• bernhardoj | Contributor | 0

[melvin-bot]

Triggered auto assignment to @srikarparsi (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.

[kbecciv]

We think that this bug might be related to #vip-vsb

[thienlnam]

Will take this over since it's related to track - feel free to re-assign if you are interested

[thienlnam]

Doesn't look like it needs to be a blocker - and we can probably make this external