[Payment due 2024-05-14][$250] iOS - Track expense - Swiping to right on invite page does not return to workspace chat

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

Action Performed:

1. Launch New Expensify app.
2. Go to self DM.
3. Go to + > Track expense.
4. Create a track scan expense.
5. From the whisper, select Share it with my accountant.
6. Select a workspace > Click Submit.
7. Tap back button on the Invite member RHP.
8. Note that it returns to the workspace chat.
9. Repeat Step 3 to 6.
10. Instead of using the back button, swipe to right (iOS) to dismiss the invite page.

Expected Result:

App will return to workspace chat.

Actual Result:

App returns to self DM.

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

Bug6460161_1713958475686.RPReplay_Final1713957671.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b51c4bf06d4563af
• Upwork Job ID: 1790541614263488512
• Last Price Increase: 2024-05-15

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @kadiealexander

[melvin-bot]

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

[mountiny]

Seems like this is coming from #40740 that did not fix the flow completely @bernhardoj can you please follow up with fix for this? could not assign you without you commenting here. Thanks!