You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-05-15] [Due for payment 2026-05-13] Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely #89682
Version Number: 9.3.67-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:#87726 Email or phone of affected tester (no customers):josdjnosdjionjsdonjisod@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Samsung Galaxy S25 FE / Android 16 App Component: Money Requests
Action Performed:
Launch Expensify app.
Open FAB > Track distance > Odometer.
Enter start and end reading.
Add a receipt to start reading.
Tap Save for later.
Kill and relaunch the app.
Open FAB > Track distance > Odometer.
Tap on the receipt added from Step 4.
Expected Result:
Receipt will be visible after relaunching app.
Actual Result:
Receipt is not visible after relaunching app and it loads infinitely.
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #87726 - "Add Save for later to Odometer screen" by @jakubkalinski0 (High confidence) Related Issues: None
Recommendation: REVERT
PR #87726 introduced a new "Save for later" feature for the Odometer screen that is directly reproducing this bug. The feature does not exist in production, reverting the PR removes the broken behavior entirely without risk of a production regression.
Assigned: @jakubkalinski0 (PR author), @Julesssss, @DylanDylann (approving reviewers) Labels: DeployBlockerCash kept (frontend App PR caused the issue). DeployBlocker removed — no backend change is needed.
The bug reproduces the exact new flow introduced by PR [Odometer] Add save for later functionality #87726: FAB > Track distance > Odometer > add receipt > Save for later > kill & relaunch > open Odometer > tap receipt = infinite load.
Affected files from the PR that relate to the bug:
src/libs/actions/OdometerTransactionUtils.ts — introduces saveOdometerDraft, hydrateOdometerDraftIntoTransaction, deserializeOdometerDraftImage, and serializeOdometerDraftImage.
src/hooks/useOdometerDraftHydrator.ts — new hook responsible for re-hydrating persisted draft images back into the transaction on mount.
src/hooks/useRestartOnOdometerImagesFailure/index.ts — significantly modified to co-operate with the new draft; now waits for odometerDraftStatus to resolve before proceeding.
src/pages/iou/request/step/IOURequestStepDistanceOdometer.tsx — wires the "Save for later" button and integrates useOdometerDraftHydrator.
src/ONYXKEYS.ts — adds the new ODOMETER_DRAFT Onyx key.
The PR modifies all files in the distance-odometer request flow that handle receipt images and draft persistence.
Root Cause
On Android (native), the PR stores image file URIs directly in the persisted ODOMETER_DRAFT Onyx key (the code path getPlatform() !== CONST.PLATFORM.WEB returns the URI as-is rather than converting to base64). After the app is killed and relaunched, the draft URI is rehydrated into the transaction via hydrateOdometerDraftIntoTransaction. However, when the user taps the receipt thumbnail, the image viewer attempts to load from that URI. The useRestartOnOdometerImagesFailure hook guards on hasVerifiedBlobs, and the blob-check path for native file URIs (not blob: prefixed) may never mark asyncVerificationPassed as true — specifically the updated code now filters urlsToCheck only to entries with blob: prefixed paths, meaning an empty array flows through Promise.all immediately, yet the component may still render a stuck loading indicator because the receipt source URI from the draft is a stale Android content URI that is no longer resolvable after a full app restart. The infinite loading is the fallback UI when the image cannot be fetched.
changed the title [-]Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/-][+][Due for payment 2026-05-13] Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/+]on May 6, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.67-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
changed the title [-][Due for payment 2026-05-13] Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/-][+][Due for payment 2026-05-15] [Due for payment 2026-05-13] Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/+]on May 8, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.68-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon May 6, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #87726
melvin-bot commentedon May 6, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 6, 2026
👋 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:
OSBotify commentedon May 6, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #87726 - "Add Save for later to Odometer screen" by @jakubkalinski0 (High confidence)
Related Issues: None
Recommendation: REVERT
PR #87726 introduced a new "Save for later" feature for the Odometer screen that is directly reproducing this bug. The feature does not exist in production, reverting the PR removes the broken behavior entirely without risk of a production regression.
Assigned: @jakubkalinski0 (PR author), @Julesssss, @DylanDylann (approving reviewers)
Labels:
DeployBlockerCashkept (frontend App PR caused the issue).DeployBlockerremoved — no backend change is needed.Detailed Analysis
Evidence
If this was caught during regression testingfield references that PR URL).Verification
src/libs/actions/OdometerTransactionUtils.ts— introducessaveOdometerDraft,hydrateOdometerDraftIntoTransaction,deserializeOdometerDraftImage, andserializeOdometerDraftImage.src/hooks/useOdometerDraftHydrator.ts— new hook responsible for re-hydrating persisted draft images back into the transaction on mount.src/hooks/useRestartOnOdometerImagesFailure/index.ts— significantly modified to co-operate with the new draft; now waits forodometerDraftStatusto resolve before proceeding.src/pages/iou/request/step/IOURequestStepDistanceOdometer.tsx— wires the "Save for later" button and integratesuseOdometerDraftHydrator.src/ONYXKEYS.ts— adds the newODOMETER_DRAFTOnyx key.Root Cause
On Android (native), the PR stores image file URIs directly in the persisted
ODOMETER_DRAFTOnyx key (the code pathgetPlatform() !== CONST.PLATFORM.WEBreturns the URI as-is rather than converting to base64). After the app is killed and relaunched, the draft URI is rehydrated into the transaction viahydrateOdometerDraftIntoTransaction. However, when the user taps the receipt thumbnail, the image viewer attempts to load from that URI. TheuseRestartOnOdometerImagesFailurehook guards onhasVerifiedBlobs, and the blob-check path for native file URIs (not blob: prefixed) may never markasyncVerificationPassedas true — specifically the updated code now filtersurlsToCheckonly to entries withblob:prefixed paths, meaning an empty array flows throughPromise.allimmediately, yet the component may still render a stuck loading indicator because the receiptsourceURI from the draft is a stale Android content URI that is no longer resolvable after a full app restart. The infinite loading is the fallback UI when the image cannot be fetched.7 remaining items
allgandalf commentedon May 6, 2026
tffff, sorry didn't mean to post
IuliiaHerets commentedon May 6, 2026
Xiaomi Redmi Note 10 / Android 12
App 9.3.67-11
Not repro
Screenrecorder-2026-05-06-21-30-24-689.mp4
[-]Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/-][+][Due for payment 2026-05-13] Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/+]melvin-bot commentedon May 6, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 6, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.67-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-05-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 6, 2026
@DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[-][Due for payment 2026-05-13] Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/-][+][Due for payment 2026-05-15] [Due for payment 2026-05-13] Android - Odometer - Receipt is not visible after relaunching app and it loads infinitely[/+]melvin-bot commentedon May 8, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.68-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-05-15. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 8, 2026
@DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]