-
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
[HOLD for payment][$1000] Chat - "Report no longer exists" message upon removing image that has deleted thread #19559
Comments
Triggered auto assignment to @conorpendergrast ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~0170002ec496e4cb5d |
Current assignee @conorpendergrast is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Triggered auto assignment to @cristipaval ( |
Reproduced on Staging and Production, by the way |
I think rendering doesn't seem to work reliably. |
📣 @JavSFDev! 📣
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Empty image returned with the error "Report no longer exists" after deletion. What is the root cause of that problem?After creating & leaving the thread, then deleting the attachment So, we update Onyx with the
It looks like even though the back-end responds with this data, the attachment is actually deleted, so after deleting the data in the local database & refreshing the page, the message dissapears. What changes do you think we should make in order to solve the problem?Have someone from back-end investigate step by step the call for this case in order to see where the problem occurs. |
I think this issue might have the same root cause as this one. Maybe we could put it on hold and test it again when the other one gets fixed? What do you think @mananjadhav ? |
Yeah I agree, we should put this one on Hold. |
On hold for #19078! |
Similar issue reported here - #19707 - do you think we could combine these into one job? cc @mananjadhav @cristipaval |
The issues are different, but they might have the same root cause. My recommendation is to also put yours on hold for this one. What do you @mananjadhav think? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
friendly bump, @anmurali |
👀 |
I'll ping @anmurali internally. She was ooo last Friday that's why I think this one got delayed. |
@anmurali, @cristipaval Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Triggered auto assignment to @conorpendergrast ( |
This comment was marked as outdated.
This comment was marked as outdated.
@conorpendergrast, could you please handle the payment here? 🙏 I discussed with @anmurali on NewDot and she is swamped these days. |
This is the only payment due here, @conorpendergrast. |
Absolutely! |
Paid and contract ended. Good to close @cristipaval ? |
Thanks! Let's close it. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Image removed successfully without any error
Actual Result:
Empty image returned with the error "Report no longer exists" after deletion
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.17.2
Reproducible in staging?: Yes
Reproducible in production?: yes
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
Notes/Photos/Videos: Any additional supporting documentation
Recording.2819.mp4
Removed.Image.Thread.mp4
Expensify/Expensify Issue URL:
Issue reported by: @kerupuksambel
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684468035059069
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: