-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Submit Expense - PDF files can not be added to scan expense on mobile apps #40486
Comments
Triggered auto assignment to @blimpich ( |
👋 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:
|
This is fixed in this PR. |
Not a blocker, since its likely already fixed by a PR that hasn't been deployed to staging yet, and is also not a huge bug. I will retest this once #40351 has been deployed to staging and confirm that it is fixed. |
Not overdue, still waiting for that PR to be deployed to staging and ideally production before retesting this and closing. |
@blimpich Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Is fixed in staging now, just tested. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.63-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #36314
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The PDF file can be added to the scan receipt and the next part of the flow appears without issues
Actual Result:
An error message appears blocking the user from adding a PDF file for scanning
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6453574_1713443618776.RPReplay_Final1713443301.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: