[HOLD for payment 2024-12-09] [HOLD for payment 2024-12-07] Categorize it -Upgrade success view opens when navigating back from category list/confirm page

[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: 9.0.68-2
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): applausetester+232803@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

• Account has no workspace.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Track a manual expense.
4. Tap Categorize it.
5. Tap Upgrade.
6. Tap Got it, thanks.
7. Tap app back button.
8. Note that it still opens upgrade success view.
9. Tap Got it, thanks.
10. Select a category.
11. Tap app back button on the confirmation page.
12. Note that it still opens upgrade success view.
13. Tap app back button again.
14. Note that now only category list will open.

Expected Result:

In Step 8 and 12, upgrade success view should be removed from the navigation path once "Got it, thanks" is tapped (similar to what is done here #52091).

Actual Result:

In Step 8 and 12, upgrade success view opens when navigating back to the previous page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6679799_1732871295619.ScreenRecording_11-29-2024_17-00-20_1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

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

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

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