Odometer-App navigates to an empty page when tapping on add odometer photo button

[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.17-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #81906
Email or phone of affected tester (no customers): applausetester+21126@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iOS 26.1 / iPhone 13, Android 11/Tecno Spark 8
App Component: Money Requests

Action Performed:

1. Log in as a user with the odometer expenses beta (An epensifail account)
2. Tap on global create > Track distance > Odomter
3. Add start and end readings
4. Tap on the "Odometer start photo" button next to the start reading field
5. Navigate back and tap on "Odometer end photo" button next to the end reading field

Expected Result:

The Upload receipt page is opened (Web behaviour)

Actual Result:

The user is navigated to an empty page

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7074440_1770801624991.video_2026-02-11_12-12-49.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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

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