Report - Amount shows "0,00" and no "Pending" label on distance if expense is created offline

[jponikarchuk]

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.9.1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-3608/folder/13176744/41237148/1149844193
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.
Prerequisite 2: Distance expense previously created so waypoints can be available while offline.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Turn off internet connection.
4. Tap on "+" button and select "Track Distance"
5. Select "Map" and add start and finish waypoints.
6. Tap on "Next"
7. Note that amount shows "0,00" on details page and "Distance" field doesn´t show a "Pending" label.
8. Finish the creation flow.
9. Open the report of the just created expense.
10. Note that amount still shows "0,00" and "Distance" field still doesn´t show a "Pending" label.

Expected Result:

While creating a distance expense while offline, "Amount" field should be empty on details page and "Distance" field should show a "Pending" label.

Actual Result:

While creating a distance expense while offline, "Amount" field shows "0,00" on details page and "Distance" field is displayed empty without a "Pending" label.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @lakchote (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[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: #79914 - "Create GPS expenses using captured data" by @GCyganek (High confidence)
Related Issues: None

Recommendation: REVERT

PR #79914 introduced GPS distance expense functionality but inadvertently broke offline MAP distance expense creation. The fix is simple but the PR is large and recently merged, making a revert the safest option to unblock the deploy.

Labels: Removed DeployBlocker label (this is a frontend bug, not a backend bug)

📋 Detailed Analysis

Evidence

The bug occurs when creating a distance expense offline using the MAP option (not GPS, not manual, not odometer). The amount shows "0,00" and the Distance field shows no "Pending" label.

PR #79914 was merged on January 24, 2026, at 03:27:23 UTC and is part of the current staging deploy (9.3.9-1). This PR adds GPS distance expense functionality and makes significant changes to distance request handling.

Verification

I examined src/pages/iou/request/step/IOURequestStepConfirmation.tsx line 256:

Before PR #79914:

const transactionDistance = isManualDistanceRequest || isOdometerDistanceRequest ? (transaction?.comment?.customUnit?.quantity ?? undefined) : undefined;

After PR #79914:

const isGPSDistanceRequest = isGPSDistanceRequestTransactionUtils(transaction);
const transactionDistance = isManualDistanceRequest || isOdometerDistanceRequest || isGPSDistanceRequest ? (transaction?.comment?.customUnit?.quantity ?? undefined) : undefined;

This change means that for MAP distance requests (the regular "Track Distance" flow with waypoints), transactionDistance is set to undefined.

When creating a distance request offline, this flow is triggered:

1. User creates MAP distance expense offline
2. transactionDistance = undefined (because it's not manual/odometer/GPS)
3. createDistanceRequest() is called with distance: undefined
4. The distance parameter is sent to the API as undefined (line 7630 in src/libs/actions/IOU/index.ts)
5. Result: Amount shows "0,00", Distance field shows no "Pending" label

Root Cause

PR #79914 added support for GPS distance requests but incorrectly assumed that all distance requests that are not manual, odometer, or GPS should have undefined distance. This broke the existing MAP distance request flow, which needs the distance value from transaction?.comment?.customUnit?.quantity to properly calculate the amount and show the pending state offline.

The correct fix would be to include MAP distance requests in the condition:

const transactionDistance = isManualDistanceRequest || isOdometerDistanceRequest || isGPSDistanceRequest || isMapDistanceRequest ? (transaction?.comment?.customUnit?.quantity ?? undefined) : undefined;

However, given the size and complexity of PR #79914 (26 files changed, 433 additions), and the fact that it was just merged 3 days ago, reverting is the safer option to quickly unblock the deploy.

[lakchote]

I confirmed that reverting #79914 solves the issue.

cc @blazejkustra @jakubkalinski0 @AndrewGable @dukenv0307 @JmillsExpensify @GCyganek