-
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
[$250] Critical: 404 error for old receipts #52777
Comments
Triggered auto assignment to @joekaufmanexpensify ( |
Splitting the receipt part of this GH here. |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Discussions on this bug are ongoing here |
@youssef-lr, @joekaufmanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@youssef-lr do you think we'll be able to raise a PR here soon? |
Yes! On it today |
This is fixed. |
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:
Reproducible in staging?: Needs Reproducing
Reproducible in production?: Needs Reproducing
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @heyjennahay
Slack conversation (hyperlinked to channel name): ts_external_expensify_migrate
Action Performed:
Prerequisite: Login as a expelled member of workspace and paymant received for submitted expense
Expected Result:
Receipts displayed in preview
Actual Result:
A 404 error displayed for receipt images
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
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @dominictbThe text was updated successfully, but these errors were encountered: