Expense - RHP opens add distance rate page instead of distance rate list after upgrading WS

[nlemma]

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.20-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #71474
Email or phone of affected tester (no customers): sdoijsdnoisjniojs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Account has self DM and does not have a workspace.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Click + > Track distance > Manual.
4. Enter amount > Next.
5. On confirm page, click Rate.
6. Click Upgrade.
7. Click Got it, thanks.

Expected Result:

RHP will open distance rate list.

Actual Result:

RHP opens add distance rate page instead of distance rate list after upgrading workspace.

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

Bug6959767_1759179762287.Screen_Recording_2025-09-30_at_04.59.28.mp4

View all open jobs on GitHub

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

[nkdengineer]

Proposal

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

RHP opens add distance rate page instead of distance rate list after upgrading workspace.

What is the root cause of that problem?

The user goes back to the new distance-rate page.

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

Line 89 in 442aa36

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?

We should go back to the distance-rate step

if (shouldSubmitExpense) {
    Navigation.navigate(ROUTES.MONEY_REQUEST_STEP_DISTANCE_RATE.getRoute(action, CONST.IOU.TYPE.TRACK, transactionID, expenseReportID));
    return;
}

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

Line 89 in 442aa36

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

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

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.

[dominictb]

Coming from #69392, I can confirm this is expected. This is part of the distance rate upgrade flow.

cc @neil-marcellini