[Due for payment 2026-05-07] Web - Distance - App stuck on E screen after refresh on confirm odometer page

[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: v9.3.62-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #86023
Email or phone of affected tester (no customers): leungbratt6+2304@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 10/Chrome
App Component: Money Requests

Action Performed:

1. Open the New Dot app
2. Click FAB -> Track Distance
3. Start an odometer expense, add both readings, capture both odometer images, and proceed to the confirmation screen
4. When on the confirmation screen, refresh the browser page

Expected Result:

Verify that the app detects the expired blob URLs and redirects you back to the start of the odometer flow (you should see a completely empty odometer tab). Step 13 in PR is fail

Actual Result:

App stuck on E screen, and the page becomes unresponsive

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7137111_1776995603657.86023_stuck.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @DylanDylann

[melvin-bot]

@Julesssss recently merged #86023, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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