Scan - Missing amount required violation, Amount is still empty after entering 0

[nlemma]

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: 9.2.29-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: #71583
Email or phone of affected tester (no customers): sdionjsdoisjdos@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a manual expense and a scan expense with invalid receipt in workspace chat.
4. After scanning fails, open the scan expense thread.
5. Enter merchant.
6. Click Amount.
7. Enter 0 and save it.

Expected Result:

When the scanning fails, amount required violation will be shown under Amount, because"Missing amount" violation is shown on the expense row.
After entering 0 amount, the field will show 0.00.

Actual Result:

When the scanning fails, amount required violation is not shown.
After entering 0 amount, the field is still empty.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6970640_1760095994370.Screen_Recording_2025-10-10_at_19.32.44.mp4

Bug6970640_1760095162060.Screen_Recording_2025-10-10_at_19.17.15.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @MarioExpensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

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