[HOLD for Payment 2024-09-06][$250] Navigation - black page when Navigating back from invited workspace chat

[IuliiaHerets]

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: v9.0.18-0
Reproducible in staging?: Y
Reproducible in production?: N
Issue was found when executing this PR #45390
Email or phone of affected tester (no customers): dave0123seife@gmail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Log in as User A, an account that owns a workspace
2. Invite B, a user that does not yet have an Expensify account
3. Check B's email for the invitation
4. Open the new.expensify.com link from the email in a different browser
5. Navigate back from the workspace chat (On Web: decrease the window size so you can get the back button)

Expected Result:

Navigating back takes you to LHN

Actual Result:

Navigating back takes you to a black page

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6565161_1723109964049.1723083220385_ad8ee684-0ca8-46b9-8c55-76efc6f081bb.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01502c96e8462645b6
• Upwork Job ID: 1821576366200920163
• Last Price Increase: 2024-08-15
• Automatic offers:
• rayane-djouah | Reviewer | 103586817
• nkdengineer | Contributor | 103586819

Issue Owner

Current Issue Owner: @miljakljajic

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

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

[IuliiaHerets]

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