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-03-31] [$250] Scan - Unexpected error when delete cropped receipt #83728
Version Number: v9.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):gocemate+b21549011@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Windows 10/Chrome App Component: Other
Action Performed:
Go FAB > Create expense > Scan
Upload or capture an image receipt
On the confirmation page, click on the receipt to open the receipt modal
Verify that the crop button appears
Click on the crop button
Crop the image and click on the save button
Verify that the image is cropped
Open a scan expense
Click on the receipt
Verify that the crop button appears
Click on the crop button
Crop the image and click on the save button
Verify that the image is cropped
Go to 3-dot menu> Delete
Expected Result:
Receipt should be deleted and no errors should appear
Actual Result:
Unexpected error appears when delete cropped receipt
Demoting this from being a deploy blocker since it's an edge case that only happens with partial transactions and it also occurs with the replace flow. Going to keep the external label.
It was not a regression as a result of the crop PR, it was an existing bug.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: Not needed
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Issue is ready for payment but no BZ is assigned. @mallenexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
Activity
melvin-bot commentedon Feb 27, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #81380
melvin-bot commentedon Feb 27, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 27, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (
External)melvin-bot commentedon Feb 27, 2026
Triggered auto assignment to @stephanieelliott (
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.53 remaining items
trjExpensify commentedon Mar 31, 2026
Okay, so given this..
It was not a regression as a result of the crop PR, it was an existing bug.
@parasharrajat can we get the BZ checklist please.
parasharrajat commentedon Mar 31, 2026
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: Remove BETA_ZERO_EXPENSES #80511 (comment)
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: Not needed
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/619557
Regression Test Proposal
Precondition:
Test:
Test 1
Test 2
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-d36a-ac31-a581-36438f4ba924melvin-bot commentedon Mar 31, 2026
Issue is ready for payment but no BZ is assigned. @mallenexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
melvin-bot commentedon Mar 31, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Apr 1, 2026
Payment Summary
Contributor: @nkdengineer due $250 via NewDot
Contributor+: @parasharrajat due $250 via NewDot
^ Test case created
I think/hope that's correct, comment/reopen if not
parasharrajat commentedon Apr 20, 2026
Payment requested as per #83728 (comment)
twisterdotcom commentedon Apr 22, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-a499-a8f1-b359-dbe10db70874garrettmknight commentedon Apr 23, 2026
$250 approved for @parasharrajat