Scan - Broken expense report is created when paying expense that have manual and scan requests

[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: 1.4.9-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:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

Precondition: There are 2 manual and 2 scan requests in the workspace chat

1. [Admin] Pay the request in the workspace chat with member
2. [Member] Go to the workspace chat
3. [Member] Tap on the IOU preview which contains the scanning requests

Expected Result:

The expense report appears normal without issue

Actual Result:

The expense report is broken. One of the scanning preview is at the top of the page with infinite skeleton loading

Workaround:

Unknown

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

Bug6304811_1701973958285.20231208_003514.mp4

View all open jobs on GitHub

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

[melvin-bot]

Triggered auto assignment to @stitesExpensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[lanitochka17]

Production:

20231208_005300.mp4

[yuwenmemon]

Unable to reproduce on staging from 3 different engineers so removing the label. Keeping the issue open though!

[melvin-bot]

@stitesExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@stitesExpensify Eep! 4 days overdue now. Issues have feelings too...

[stitesExpensify]

Still unable to reproduce. Closing.