Odometer expenses starting at 0 miles lose their original readings

[Julesssss]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported: here

Action Performed:

• 1st expense
• FAB > Create Distance expense
• Select Odometer tab
• Enter any NON-ZERO start reading
• Enter a larger end reading
• Create expense
• Open expense, look at description
• It should contain original odometer readings: $63.08 for 87.00 mi @ $0.725 / mi (odometer start: 1, odometer end: 88)
• 2nd expense
• FAB > Create Distance expense
• Select Odometer tab
• Enter start reading of ZERO
• Enter a larger end reading
• Create expense
• Open expense, look at description
• It should contain original odometer readings: $63.08 for 87.00 mi @ $0.725 / mi (odometer start: 0, odometer end: 88)

Expected Result:

It should contain original odometer readings:

$63.08 for 87.00 mi @ $0.725 / mi (odometer start: 1, odometer end: 88)

Actual Result:

It is missing the odometer original values:

$63.80 for 88.00 mi @ $0.725 / mi

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

Expense 1

Expense 2

View all open jobs on GitHub

[Julesssss]

I know the issue, it's backend and I'll fix myself.

[Julesssss]

PR: https://github.com/Expensify/Web-Expensify/pull/52908

[Julesssss]

PR merged awaiting deployment

[melvin-bot]

@Julesssss Whoops! This issue is 2 days overdue. Let's get this updated quick!