[$250] Android - Receipt - After saving a cropped receipt, a bigger part of the image disappears.

[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.3.27.2
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): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the Expensify app.
2. Open any workspace chat.
3. Create a manual expense.
4. Open the just created expense and tap on the "+" button on receipt thumbnail.
5. Upload an image of a receipt.
6. Click on the receipt to open the receipt modal.
7. Tap on the "Crop" button.
8. Select a zone to crop and save the image.
9. Reopen the receipt.
10. Note that the zone that was cropped from the image is bigger than the selected one.

Expected Result:

The part of a receipt that the user cropped, has to remain the same after saving the edition.

Actual Result:

After cropping and saving a receipt, a bigger zone of the image disappears, and not only the part that the user selected to crop.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7090575_1772247439759.Crop.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @Pujan92

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022027683230905824208
• Upwork Job ID: 2027683230905824208
• Last Price Increase: 2026-02-28

[melvin-bot]

@trjExpensify recently merged #81380, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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