Different unit is shown on table and Distance field after changing unit and adding new split

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.46-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: #92055
Email or phone of affected tester (no customers): sdsjodijnsdojsosjio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Enable Distance rates.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a distance expense.
4. Open the expense.
5. Click More > Split > Save.
6. Go to workspace settings > Distance rates.
7. Click Settings > Unit > change to Kilometer.
8. Go back to workspace chat.
9. Open any split.
10. Click Amount.
11. Click Add split.
12. Enter amount on the new split and save the splits.
    → Merchant field for the new split shows the new unit.
13. Open the new split.
    → Distance field still shows the old unit.

Expected Result:

In Step 12, merchant field for the new split should show the old unit.

Actual Result:

In Step 12, merchant field for the new split shows the new unit.
In Step 13, Distance field on the split details page shows the old unit.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7221277_1785359614461.6.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7221277

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/45372c8929a1775452dea95120b6e0049065fdcaf28b8f4f538139a5c996b93a

[melvin-bot]

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

[melvin-bot]

@lakchote @dmkt9 you have been assigned to this deploy blocker because you reviewed the offending PR: #92055

[melvin-bot]

@ZhenjaHorbach you have been assigned to this deploy blocker because you authored the offending PR: #92055

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