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-07] Web - Distance - App stuck on E screen after refresh on confirm odometer page #88678
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:
Open the New Dot app
Click FAB -> Track Distance
Start an odometer expense, add both readings, capture both odometer images, and proceed to the confirmation screen
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
👋 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: #86023 - "[Odometer] Blob URL loss detection" by @jakubkalinski0 (High confidence) Related Issues: #84707
Recommendation: REVERT
The PR introduced new logic to detect expired blob URLs on page refresh and navigate the user back to the start of the odometer flow. Test step 13 in the bug report directly references step 13 from this PR's own QA steps (refresh on the confirmation screen), which is the exact scenario that is failing — instead of redirecting to the start of the odometer flow, the app gets stuck on the "E" loading screen and becomes unresponsive. The fix is in the App codebase, so a revert of this PR is the appropriate action.
Assigned: @jakubkalinski0 (PR author), @DylanDylann (approving reviewer), @Julesssss (approving reviewer) Labels: DeployBlockerCash kept. DeployBlocker should be removed — the issue is staging-only and the fix is in the App (frontend), not the backend.
📋 Detailed Analysis
Evidence
The issue body explicitly says "Step 13 in PR is fail" — this directly references test step 13 from PR [Odometer] Blob URL loss detection #86023's QA steps: "When on confirmation screen refresh the browser page. Verify that the app detects the expired blob URLs and redirects you back to the start of the odometer flow."
PR [Odometer] Blob URL loss detection #86023 was merged on 2026-04-23 (yesterday) and the issue was filed on 2026-04-24 during regression QA of the current staging deploy.
The issue is reproducible on staging but NOT on production, confirming it was introduced in a staging-only PR.
The affected files are src/hooks/useRestartOnOdometerImagesFailure/index.ts and src/pages/iou/request/step/confirmation/OdometerReceiptStitcher.tsx, both newly added/modified by PR [Odometer] Blob URL loss detection #86023.
The bug specifically manifests on the confirmation screen (step IOURequestStepConfirmation), which is precisely where PR [Odometer] Blob URL loss detection #86023 added the useRestartOnOdometerImagesFailure hook call.
PR [Odometer] Blob URL loss detection #86023 also modified OdometerReceiptStitcher.tsx (the confirmation screen stitching component) to add a pre-flight blob URL check that could race or fail to navigate correctly.
Root Cause
When the user refreshes the browser on the odometer confirmation screen, the useRestartOnOdometerImagesFailure hook (introduced by PR #86023) is supposed to detect expired blob:// URLs and navigate back to the start of the flow. Instead, the app gets stuck on the "E" (loading) screen and becomes unresponsive. The likely cause is an interaction between the hook's async blob-check promise and the OdometerReceiptStitcher component's own pre-flight blob check — both run simultaneously on mount after a refresh. The clearOdometerDraftTransactionState call (which clears Onyx data) may fire while the stitcher is still trying to stitch, causing navigation or state inconsistency that leaves the page in an unrecoverable loading state.
changed the title [-]Web - Distance - App stuck on E screen after refresh on confirm odometer page[/-][+][Due for payment 2026-05-07] Web - Distance - App stuck on E screen after refresh on confirm odometer page[/+]on Apr 30, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.64-31 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 Apr 24, 2026
@Julesssss recently merged #86023, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Apr 24, 2026
Triggered auto assignment to @flodnv (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 24, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 24, 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 Apr 24, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #86023 - "[Odometer] Blob URL loss detection" by @jakubkalinski0 (High confidence)
Related Issues: #84707
Recommendation: REVERT
The PR introduced new logic to detect expired blob URLs on page refresh and navigate the user back to the start of the odometer flow. Test step 13 in the bug report directly references step 13 from this PR's own QA steps (refresh on the confirmation screen), which is the exact scenario that is failing — instead of redirecting to the start of the odometer flow, the app gets stuck on the "E" loading screen and becomes unresponsive. The fix is in the App codebase, so a revert of this PR is the appropriate action.
Assigned: @jakubkalinski0 (PR author), @DylanDylann (approving reviewer), @Julesssss (approving reviewer)
Labels:
DeployBlockerCashkept.DeployBlockershould be removed — the issue is staging-only and the fix is in the App (frontend), not the backend.📋 Detailed Analysis
Evidence
StagingDeployCashchecklist (Deploy Checklist: New Expensify 2026-04-23 #88633).Verification
src/hooks/useRestartOnOdometerImagesFailure/index.tsandsrc/pages/iou/request/step/confirmation/OdometerReceiptStitcher.tsx, both newly added/modified by PR [Odometer] Blob URL loss detection #86023.useRestartOnOdometerImagesFailurehook call.OdometerReceiptStitcher.tsx(the confirmation screen stitching component) to add a pre-flight blob URL check that could race or fail to navigate correctly.Root Cause
When the user refreshes the browser on the odometer confirmation screen, the
useRestartOnOdometerImagesFailurehook (introduced by PR #86023) is supposed to detect expired blob:// URLs and navigate back to the start of the flow. Instead, the app gets stuck on the "E" (loading) screen and becomes unresponsive. The likely cause is an interaction between the hook's async blob-check promise and theOdometerReceiptStitchercomponent's own pre-flight blob check — both run simultaneously on mount after a refresh. TheclearOdometerDraftTransactionStatecall (which clears Onyx data) may fire while the stitcher is still trying to stitch, causing navigation or state inconsistency that leaves the page in an unrecoverable loading state.17 remaining items
Julesssss commentedon Apr 27, 2026
Resolved with this PR, I'll get it merged and CP'd
Julesssss commentedon Apr 27, 2026
I verified the fix and cherry-picked it to staging. Just awaiting retesting from QA.
Julesssss commentedon Apr 27, 2026
Fixed on staging 🎉
mitarachim commentedon Apr 27, 2026
Deploy Blocker #89008 was identified to be related to the PR #88702 that attempted to fix this issue.
melvin-bot commentedon Apr 28, 2026
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.
[-]Web - Distance - App stuck on E screen after refresh on confirm odometer page[/-][+][Due for payment 2026-05-07] Web - Distance - App stuck on E screen after refresh on confirm odometer page[/+]melvin-bot commentedon Apr 30, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 30, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.64-31 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-07. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 30, 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]