[HOLD for payment 2024-07-10] [HOLD for payment 2024-07-02] [$250] Scan - Existing expense is removed when dismissing receipt error

[kbecciv]

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.0.1-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4662109
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit a manual expense without receipt.
4. Go to transaction thread.
5. Tap Receipt thumbnail.
6. Add a corrupted PDF as the receipt (attached below).
7. Wait for the error to show up (re-add the corrupted file again if it disappears).
8. Dismiss the error.
   PDF file
   LARGE PDF FILE corrupted.pdf

Expected Result:

The "existing" expense should not be deleted because user is only adding the receipt. It should be deleted only when user adds corrupted PDF when creating the expense. In this case, the expense is already created and dismissing the error should only removed the receipt and not the expense together.

Actual Result:

The "existing" expense is removed after the receipt error is dismissed.

Workaround:

n/a

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6522699_1719221436204.20240624_172248.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01ef5c51a3c66fea79
• Upwork Job ID: 1805206123739282150
• Last Price Increase: 2024-06-24
• Automatic offers:
• jjcoffee | Reviewer | 102860123
• bernhardoj | Contributor | 102860126

Issue Owner

Current Issue Owner: @Christinadobrzyn

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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 @cristipaval (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[kbecciv]

We think that this bug might be related to #wave-collect - Release 1