-
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 - "Receipt scanning failed" is shown when "Unknown merchant" is not considered an error #33418
Comments
👋 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:
|
Triggered auto assignment to @tylerkaraszewski ( |
It looks like this error is being displayed here: https://github.com/Expensify/Auth/blob/main/auth/command/EditMoneyRequest.cpp#L375-L403 @Gonals @sobitneupane is this the expected behavior when the user selects "Merchant is unclear"? I feel like it's a bit awkward, since they already specified that they weren't able to get a merchant from the receipt. Regardless, I'm not going to block deploy on this–this can be fixed in a subsequent PR. |
@Gonals Whoops! This issue is 2 days overdue. Let's get this updated quick! |
You are very right. I'll fix that |
@Gonals Whoops! This issue is 2 days overdue. Let's get this updated quick! |
This is done |
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.15-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:
Issue found when executing PR #33220
Action Performed:
Expected Result:
Since "Unknown merchant" is no longer considered an error, it will not show "Receipt scanning failed" message
Actual Result:
It still shows "Receipt scanning failed" message when "Unknown merchant" is not considered an error
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: