[$250] Scan - Save button loads infinitely when photo is cropped to the smallest size

[mitarachim]

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.3.27-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: #81380
Email or phone of affected tester (no customers): osidnjodjosijsoji@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Open staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Scan.
4. Upload a photo.
5. On confirm page, click on the receipt.
6. Click Crop.
7. Crop it to the smallest and tap Save.
8. Repeat Step 6 to 7 a few times.

Expected Result:

Save button will not load infinitely when photo is cropped to the smallest.
Error should show up if the smallest size is not accepted.

Actual Result:

Save button loads infinitely when photo is cropped to the smallest.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7090165_1772206230353.5.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @hungvu193

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022027413879430107482
• Upwork Job ID: 2027413879430107482
• Last Price Increase: 2026-02-27

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #81380

[melvin-bot]

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

[melvin-bot]

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

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