[Due for payment 2026-05-11] Odometer-Discard changes modal is shown after refreshing the browser and navigating away

[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: 9.3.62-10
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #88702
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: MacBook Air 15.7.4 Chrome
App Component: Money Requests

Action Performed:

1. Open the NewDot app on web
2. Click the FAB -> Track Distance -> switch to the Odometer tab
3. Enter a start odometer reading and capture a start odometer image
4. Enter an end odometer reading and capture an end odometer image
5. Refresh the browser
6. Click outside the modal or on the back button

Expected Result:

"Discard changes?" modal does not appear since the changes were removed after refreshing the browser

Actual Result:

"Discard changes?" modal appears when navigating away from Odometer flow after refreshing the browser

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7139609_1777324311911.Discard_changes.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @DylanDylann

[melvin-bot]

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

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

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.