[HOLD for payment 2024-06-13] [$250] [Guided Setup] Redirect where user was when they try to deeplink to the onboarding flow after completion

[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 reported by: Applause - Internal Team
Issue found when executing PR: #40667

Action Performed:

1. Open expensify staging app
2. Open any chat
3. Send this url https://staging.new.expensify.com/onboarding
4. Tap on the sent URL to start the onboarding flow
5. Tap on any one of the purpose options more than one time

Expected Result:

When the user already completed the guided setup flow, we should make sure we re-navigate them to the main page after they attempt to deeplink to the flow

Actual Result:

Users can go through the onboarding flow as many times as they want

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

Bug6460070_1713954299071.Screen_Recording_20240424_131955_New_Expensify.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01a5d3f767fe2611e7
• Upwork Job ID: 1783996337884426240
• Last Price Increase: 2024-04-26
• Automatic offers:
• c3024 | Reviewer | 0

[melvin-bot]

Triggered auto assignment to @flodnv (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 #wave-collect - Release 1

[mountiny]

Taking over