Infinite loading with skeleton page appear when navigating back from Navattic

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: v9.0.83-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #54824
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Samsung s10/ chrome
App Component: Other

Action Performed:

1. Navigate to https://staging.new.expensify.com
2. Login with a new account.
3. Choose any onboarding intent except "Something else".
4. Go to Concierge and click on the "Take a 2 minute tour" task.
5. Click on the tour link in the tour description.
6. Complete the Navattic tour and return to expensify

Expected Result:

The tour task is marked as complete on redirect to Concierge after completing the tour.

Actual Result:

Infinite loading with skeleton page appear when navigating back from Navattic and the tour is not marked as completed

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6710641_1736491971940.Screen_Recording_20250110_091418_Chrome.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[c3024]

Coming from my PR #54824 . I am raising a PR fixing this.