Scan split - "Receipt not verified" appears despite successful scanning in group splitting

[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: 1.4.25-4
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:

1. Go to 1:1 DM.
2. Create a scan request with a valid receipt.
3. When the scanning is complete, go to request details page.
4. Note that there is no "Receipt not verified. Please confirm accuracy." message
5. Go to a group chat.
6. Create a scan request with a valid receipt.
7. When the scanning is complete, go to request details page.

Expected Result:

There is no "Receipt not verified. Please confirm accuracy." message since the scanning is complete.

Actual Result:

"Receipt not verified. Please confirm accuracy." message shows up below receipt preview, when the scanning is complete without intervention. This issue only occurs with Scan split in group chat.

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

Bug6344089_1705398381312.bandicam_2024-01-16_17-40-17-806.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 @aldo-expensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[melvin-bot]

Triggered auto assignment to @puneetlath (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[mountiny]

@cead22 this is also related to violations it seems, not a deploy blocker added to the wave6 project in the meantime

[cead22]

The steps suggest that one receipt parsed correctly, and the other didn't, and if that's the case, the outcome is what we expect and this isn't a front end bug, but a parsing/smartscanning bug