Repository navigation
Scan - Preview of failed scan, shows "0,00" on Home despite amount field being empty. #102963
Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: 9.5.2-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: #98871
Email or phone of affected tester (no customers): ibellicotest+3215@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests
Action Performed:
Prerequisite: Account has a workspace.
- Open the Expensify app.
- Navigate to workspace chat.
- Create a scan expense with a receipt/image that will fail SmartScan.
- Wait until the scan fails.
- Open the expense details.
- Note that the "Amount" field is empty instead of showing $0.00.
- Return to chat.
- Note that no amount is displayed on expense preview either.
- Navigate to "Home" > "Recently Added"
- Note that failed scan preview shows "0,00" despite amount field on report being empty and preview on chat showing no amount.
Expected Result:
No amount should be displayed on failed scan expense preview on "Home". Behavior should be the same as expense preview on chat, where no amount is displayed.
Actual Result:
Failed scan expense preview shows "0.00" on "Recently Added" section on "Home", despite amount field being empty inside report and despite preview on chat showing no amount.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7277446_1791174092107.0_Scan_8.mp4
Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7277446
Issue Owner
Current Issue Owner: @x-dev90Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
applause-bot commentedon Oct 5, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/3775c799e557fc6e09e7fa1fdbea2150028ecec3f4d037522b71d85c77b60964
melvin-bot commentedon Oct 5, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #98871
github-actions commentedon Oct 5, 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:
melvin-bot commentedon Oct 5, 2026
@arosiclair @Ollyws you have been assigned to this deploy blocker because you reviewed the offending PR: #98871
melvin-bot commentedon Oct 5, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Oct 5, 2026
Deploy Blocker Analysis
Recommendation: Demote, and fix forward. Do not revert.
The Home "Recently Added" row also shows
0.00on production. No PR in this deploy changed that section. What's new is that the chat preview and expense details now show an empty amount. fix: show scan error instead of populating $0 amount when scan fails made that change but did not update the Recently Added row. So this is an incomplete fix, not a regression.Reverting that PR would bring back
$0.00everywhere, which is the original bug.Fix: Show an empty amount in the Recently Added row when
isFailedScanAmountPlaceholder(expense.transaction)is true. This matches the chat preview logic in TransactionPreviewUtils.ts:320-321. This fits as a follow-up from the PR author,x-dev90.Investigation details
Why it's not a regression
src/pages/home/RecentlyAddedSection/changed between production and staging.$0.00for failed scans. They agreed, so the issue reads "not reproducible on production."What the PR changed
It added
isFailedScanAmountPlaceholder()and used it in these places:Where the check is missing
getAmount()and does not check for a failed scan.convertToDisplayString(). The row then renders that0.00at line 70.No other PR on the staging checklist touches this code path.
Next Steps: Reply with
@MelvinBot implement thisto create a draft PR, or@MelvinBot <your feedback>to refine this analysis.view run
x-dev90 commentedon Oct 5, 2026
I reproduced the same behavior in production: Home → Recently Added already shows 0.00 for a failed scan. Since PR #98871 didn’t change this section, it is not regression from my PR.
I’m happy to investigate and open a follow-up PR—please assign it to me. Thanks!
Screen.Recording.2026-10-05.at.12.37.10.PM_compressed.mp4
arosiclair commentedon Oct 5, 2026
Yup not a regression here either. I'm not sure how this task should display with no amount at all though. Demoting this for now
2 remaining items
melvin-bot commentedon Oct 8, 2026
@arosiclair Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Oct 9, 2026
@arosiclair — to hire @x-dev90 on Upwork, add the External label so a job is created and the offer is sent automatically.