Distance - Error displayed after creating a distance expense offline and going online

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: v9.1.16-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5782592&group_by=cases:section_id&group_id=294997&group_order=asc
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome
App Component: Money Requests

Action Performed:

1. Go to https://staging.new.expensify.com/ and log in as a new Gmail account
2. Navigate to a workspace chat
3. Disable the internet connection
4. Click on the "+" button
5. Select "Submit expense"
6. Click on the "Distance" tab
7. Click on "Start"
8. Enter a destination - E,g "45n N Beach Rd, FL"
9. Enter a new destination
10. Enter the "Finish" address - e.g "Beach Access Path, Sunny Isles Beach, FL"
11. Click on Save
12. Click on the "Submit" button
13. Click on the expense
14. Enable the internet connection

Expected Result:

Verify the distance expense is not greyed out
Verify the map loads and displays the trip road
Verify the details of the miles and amount are displayed

Actual Result:

After creating a new distance expense offline and going online again, the distance expense displays an error. When clicking the "X" button on the error message, the expense disappears.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mountiny

[melvin-bot]

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

[jponikarchuk]

Not reproducible in Production

bandicam.2025-03-21.15-37-08-273.mp4

[isabelastisser]

Not reproducible; closing.

[isagoico]

@isabelastisser We're able to consistently reproduce this issue ad it's not reproducible in prod. Do we still want to keep it closed?

bandicam.2025-03-21.18-33-30-134.mp4

[isabelastisser]

Thanks for the heads up, @isagoico! Reopening it.

[melvin-bot]

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

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

[Gonals]

Can confirm this happens in staging, but not in prod. I haven't been able to reproduce in Dev, but that's likely just dev being dev

[mountiny]

@Gonals What was the requestID or error you got in staging?

[Gonals]

92559a0a98e4cbb3-SJC is the most recent

Extra info: If you use places you already "have" (AKA, you repeat a distance expense you already correctly created between two spots), it does not error.

[mountiny]

I am also getting an error in production - I think the RCA is that the mapbox api fails to fetch the enriched waypoints (from offline mode the points do not have lat and lon so we have to get that

[mountiny]

Seems like an issue with mapbox api - its an edge case flow though as this is only when the request was made offline and the waypoints data does not have latitude and longitude info

[mountiny]

Havent looked yet

[melvin-bot]

@isabelastisser, @mountiny Eep! 4 days overdue now. Issues have feelings too...

[mountiny]

This is a lower priority as its an edge case

[melvin-bot]

@isabelastisser @mountiny this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[mountiny]

focusing on higher priority task now

[isabelastisser]

No updates!

[mountiny]

No updates still

[mountiny]

Same

[isabelastisser]

No updates.

[mountiny]

Back from ooo, catching up

[mountiny]

still low but hoping to find some time for this soon