[Due for payment 2025-11-17] [$250] mWeb -Expense- Device back button after creating WS from rate field leads to "Upgrade" again

[mitarachim]

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.2.36-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1424/folder/18717689/49855697/965872280
Email or phone of affected tester (no customers): ibellicotest+1946@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb)
App Component: Money Requests

Action Performed:

Prerequisite: Account has a Self DM.

1. Open the staging.new.expensify.com website.
2. Navigate to Self DM.
3. Start a manual distance expense creation flow.
4. Add any distance and tap on "Next"
5. Tap on the "Rate" field.
6. Tap on "Upgrade" to create a workspace.
7. Tap on "Got It, thanks"
8. Use device´s back button.
9. Note that you land on "Upgrade" page again.
10. Tap on "Upgrade" one more time.
11. Return to "Inbox"
12. Note that two different workspaces were created.

Expected Result:

Using device´s back button after creating a workspace from the "Upgrade" page, should redirect to "Confirm Details" page again.

Actual Result:

After creating a track manual distance expense, and creating a new workspace from the "Upgrade" page on the rate option, using device´s back button leads to "Upgrade" page again.
Everytime the user lands on "Upgrade" page again, a new workspace can be created.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6981126_1761116392836.Upgrade.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021981328311168632313
• Upwork Job ID: 1981328311168632313
• Last Price Increase: 2025-10-30
• Automatic offers:
• huult | Contributor | 109316868

Issue Owner

Current Issue Owner: @bfitzexpensify

[melvin-bot]

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

Job added to Upwork: https://www.upwork.com/jobs/~021981328311168632313

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil (External)

[huult]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Device back button after creating WS from rate field leads to "Upgrade" again

What is the root cause of that problem?

We’ve already used goBack to clear the upgrade step.

App/src/pages/iou/request/step/IOURequestStepUpgrade.tsx

Line 75 in 78a8a1a

Navigation.goBack();

his issue happens because goBack hasn’t finished before navigating to the WORKSPACE_CREATE_DISTANCE_RATE page. As a result, the upgrade step page still exists, so when we go back, it returns to that page

App/src/pages/iou/request/step/IOURequestStepUpgrade.tsx

Line 86 in 78a8a1a

Navigation.navigate(ROUTES.WORKSPACE_CREATE_DISTANCE_RATE.getRoute(policyID, transactionID, expenseReportID));

What changes do you think we should make in order to solve the problem?

To fix this issue, we should queue the navigation so it only runs after goBack has completed

App/src/pages/iou/request/step/IOURequestStepUpgrade.tsx

Line 86 in 78a8a1a

Navigation.navigate(ROUTES.WORKSPACE_CREATE_DISTANCE_RATE.getRoute(policyID, transactionID, expenseReportID));

update to:

Navigation.setNavigationActionToMicrotaskQueue(() => Navigation.navigate(ROUTES.WORKSPACE_CREATE_DISTANCE_RATE.getRoute(policyID, transactionID, expenseReportID)));

Screen.Recording.2025-10-24.at.22.01.44.mov

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[rojiphil]

@huult proposal LGTM i.e. let goBack to complete before we navigate further. Let us also do the same for the remaining upgrade paths.
🎀👀🎀 C+ reviewed