[$250] Distance - After changing unit, Distance field keeps the new value with old 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): sdjoijnsdoinsjoisjio@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 in workspace settings > More features.

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 Distance.
12. Click Save.
13. Click Distance.
14. Click Save.

Expected Result:

After saving distance with new unit, Distance field should also save the new unit.

Actual Result:

After saving distance with new unit, Distance field keeps the new value with old unit.
When user reopens Distance and resaves it, the value is converted again and old unit is saved.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7089791_1772166810414.18.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @aimane-chnaif

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022027246830565122976
• Upwork Job ID: 2027246830565122976
• 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 @heyjennahay (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.