-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scan request - Unable to add amount to scan failed IOU. "Unknown merchant" shows when scan is failed #39416
Comments
Triggered auto assignment to @Christinadobrzyn ( |
We think that this bug might be related to #wave-collect - Release 1 |
@Christinadobrzyn I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
I'm not getting the same results - it looks like the details on the failed SmartScan are as expected Asking QA for a little more information on how to reproduce this. https://expensify.slack.com/archives/C9YU7BX5M/p1712116620976629 |
@Christinadobrzyn able to reproduce. Attaching video and receipt used. bandicam.2024-04-03.16-03-49-271.mp4 |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
I'm now able to get the "unknown merchant" on the failed IOU but the amount is saving properly so I'm going to close this as resolved. 2024-04-04_15-03-02.mp4 |
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: v1.4.59-0
Reproducible in staging?: y
Reproducible in production?: y
Issue found when executing PR: #39034
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The receipt amount should reflect the correct value
Actual Result:
When attempting to add an amount to a failed IOU scan, an "Unknown Merchant" appears
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6435580_1712064282172.Failed.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: