[$250] Distance is saved with new value and old unit after changing rate with different unit

[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.26-7
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: #82257
Email or phone of affected tester (no customers): shdsubhiudhbuidshs@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:

• Distance rates are enabled.
• Workspace has at least two distance rates.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a manual distance expense.
4. Open the expense.
5. Click More > Split > Save.
6. Go to workspace settings > Distance rates.
7. Click Settings > Unit.
8. Change to another unit.
9. Open any distance split from Step 5.
10. Click Amount > click highlighted row.
11. Click Rate.
12. Select another rate.
    → Distance field is converted to the correct value and unit.
13. Click Save > Save.
14. Click Distance field on the transaction thread.

Expected Result:

Distance field will show the correct value and unit in Step 12.

Actual Result:

The distance field shows the new value with old unit.
Distance editor further converts the value to the new unit.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7089781_1772165741560.17.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @suneox

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022027246443158234016
• Upwork Job ID: 2027246443158234016
• Last Price Increase: 2026-02-27

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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

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