Skip to content

[Due for payment 2026-03-31] [$250] Scan - Unexpected error when delete cropped receipt #83728

Closed

Description

@lanitochka17

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: 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:

  1. Go FAB > Create expense > Scan
  2. Upload or capture an image receipt
  3. On the confirmation page, click on the receipt to open the receipt modal
  4. Verify that the crop button appears
  5. Click on the crop button
  6. Crop the image and click on the save button
  7. Verify that the image is cropped
  8. Open a scan expense
  9. Click on the receipt
  10. Verify that the crop button appears
  11. Click on the crop button
  12. Crop the image and click on the save button
  13. Verify that the image is cropped
  14. 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

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7090194_1772208116022.Recording__381.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022027420520535674762
  • Upwork Job ID: 2027420520535674762
  • Last Price Increase: 2026-03-06

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 27, 2026
  2. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 27, 2026
  3. melvin-bot commented on Feb 27, 2026

    @melvin-bot

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

  4. melvin-bot commented on Feb 27, 2026

    @melvin-bot

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

  5. melvin-bot commented on Feb 27, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

  6. melvin-bot commented on Feb 27, 2026

    @melvin-bot

    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.

  7. 53 remaining items

  8. trjExpensify commented on Mar 31, 2026

    @trjExpensify
    Contributor

    Okay, so given this..

    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.

    @parasharrajat can we get the BZ checklist please.

  9. parasharrajat commented on Mar 31, 2026

    @parasharrajat
    Member

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [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

    1. Go to a DM chat
    2. Create a scan request with an invalid receipt
    3. After scanning, open the expense detail > click on the receipt
    4. In the receipt view, click on three dot icon
    5. Verify that no delete option

    Test 2

    1. Go to WS chat
    2. Create a scan request with a valid receipt
    3. After scanning, go offline
    4. Replace the receipt multiple times
    5. Delete the receipt
    6. Open Inspect > Network
    7. Go online
    8. Verify that in the Network tab, we only see one ReplaceReceipt API and one DetachReceipt API

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-d36a-ac31-a581-36438f4ba924
  10. melvin-bot commented on Mar 31, 2026

    @melvin-bot

    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!

  11. melvin-bot commented on Mar 31, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2027420520535674762/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  12. mallenexpensify commented on Apr 1, 2026

    @mallenexpensify
    Contributor

    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

  13. parasharrajat commented on Apr 20, 2026

    @parasharrajat
    Member

    Payment requested as per #83728 (comment)

  14. twisterdotcom commented on Apr 22, 2026

    @twisterdotcom
    Contributor

    @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-dbe10db70874
  15. garrettmknight commented on Apr 23, 2026

    @garrettmknight
    Contributor

    $250 approved for @parasharrajat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions