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-04-14] Expense - Odometer photo is closed immediately after clicking rotate #86355
Version Number: v9.3.44-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#85105 Email or phone of affected tester (no customers):applausetester+piyoh@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Windows 11 / Chrome App Component: Money Requests
Action Performed:
Preconditions: Logged in to expensifail account
Steps:
Click FAB and choose "Track distance"
Navigate to Odometer tab, fill the start reading, end reading, and add a photo to the end reading
Click next to the confirmation page
4.Click "distance" field
Click the photo that just uploaded on the end reading
Click "rotate"
7, Open the odometer end photo again
Click "rotate"
Expected Result:
in step 6, odometer end photo should stay still after clicking rotate without closed immediately, just like clicking rotate in step 8.
Actual Result:
in step 6, Odometer end photo is closed immediately after clicking rotate for the first time
I believe I already know why is that happening. Current version on main doesn't yet have the backup transaction implemented. That's basically what's blocking us from safely editing values/images in "Distance" from confirmation screen. When we rotate a photo we basically create a completely new image which gets new blob URL. When we change the single photo we call setMoneyRequestOdometerImage in TransactionReceiptModalContent, which not only saves the new image to ONYX but also takes care of cleaning stale blob URLs and immediately calls revokeOdometerImageUri. When that happens this useEffect in IOURequestStepConfirmation re-runs and verifies that the receipt isn't actually properly working (it's checking on the old receipt as the new Odometer Image wasn't yet set as a new receipt). When it detects the corrupted receipt it calls navigateToStartMoneyRequestStep and this way we land on Odometer tab once again.
// When the component mounts, if there is a receipt, see if the image can be read from the disk. If not, redirect the user to the starting step of the flow.
// This is because until the request is saved, the receipt file is only stored in the browsers memory as a blob:// and if the browser is refreshed, then
// the image ceases to exist. The best way for the user to recover from this is to start over from the start of the request process.
// skip this in case user is moving the transaction as the receipt path will be valid in that case
changed the title [-]Expense - Odometer photo is closed immediately after clicking rotate[/-][+][Due for payment 2026-04-14] Expense - Odometer photo is closed immediately after clicking rotate[/+]on Apr 7, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.52-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
Julesssss commentedon Mar 25, 2026
Not a blocker, but we'll get this resolved.
jakubkalinski0 commentedon Mar 25, 2026
I believe I already know why is that happening. Current version on main doesn't yet have the backup transaction implemented. That's basically what's blocking us from safely editing values/images in
"Distance"from confirmation screen. When we rotate a photo we basically create a completely new image which gets newblob URL. When we change the single photo we callsetMoneyRequestOdometerImageinTransactionReceiptModalContent, which not only saves the new image to ONYX but also takes care of cleaning stale blob URLs and immediately callsrevokeOdometerImageUri. When that happens thisuseEffectinIOURequestStepConfirmationre-runs and verifies that the receipt isn't actually properly working (it's checking on the old receipt as the new Odometer Image wasn't yet set as a new receipt). When it detects the corrupted receipt it callsnavigateToStartMoneyRequestStepand this way we land on Odometer tab once again.App/src/pages/iou/request/step/IOURequestStepConfirmation.tsx
Lines 623 to 681 in f0b9ae0
jakubkalinski0 commentedon Mar 25, 2026
TLDR this will be resolved here -> [Odometer] Add backup transaction for purpose of editing from confirmation. We can tag this issue under the PR and add it as a test case but besides that I don't think a separate fix is needed here
@Julesssss Should I link it in the PR description and add test steps?
DylanDylann commentedon Mar 26, 2026
Let's do it
Julesssss commentedon Mar 26, 2026
Yeah, thanks for doing that.
1 remaining item
DylanDylann commentedon Apr 3, 2026
@Julesssss Could you close this issue?
[-]Expense - Odometer photo is closed immediately after clicking rotate[/-][+][Due for payment 2026-04-14] Expense - Odometer photo is closed immediately after clicking rotate[/+]melvin-bot commentedon Apr 7, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 7, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.52-9 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-04-14. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 7, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)