Workspace-App crashes on back navigation from new workspace

[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.65-1
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+tw5535353533@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Sign up for a new account and Click on the FAB button.
2. Use the FAB button to Create a new workspace.
3. Navigate back by first clicking the website's back button, followed by the browser's back button.

Expected Result:

The app should function normally without crashing.

Actual Result:

The app crashes after navigating back as described.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6671535_1732170291816.Screen_Recording_2024-11-20_at_10.10.34_PM.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

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

[youssef-lr]

Checking!

[youssef-lr]

I can't reproduce, I think this error happened because the app failed to fully load. You can see in the recording that Concierge chat was failing to load.