Distance-Rate does not auto default to last used rate when creating distance expense in self DM

[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.3.53-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #84136
Email or phone of affected tester (no customers): sjoinjojsodidsjodjso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Enable Distance rates.
• Workspace has at least two distance rates.

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. Select another rate and click Create expense.
7. Repeat Step 2 to 6.
8. Click + > Track distance > Manual.
9. Enter amount > Next.
10. Open Rate field.

Expected Result:

Rate will auto default to the last used rate in Step 6.

Actual Result:

Rate does not auto default to the last used rate in Step 6. It still shows the "default rate".

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7123257_1775526642290.8.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #84136

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

[OSBotify]

Investigation Summary: Classification = Frontend bug. Causing PR = #84136 by @FitseTLT (High confidence). Recommendation = REVERT. PR #84136 explicitly disabled last-selected-rate logic for track distance expenses, which directly causes this regression - in DistanceRequestUtils.ts getCustomUnitRateID, when isTrackDistanceExpense=true, the lastSelectedDistanceRate check is always skipped (condition !isTrackDistanceExpense is always false). Labels: keeping DeployBlockerCash as this is a Frontend bug caused by an App PR.