-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Loading header appears when the sender deletes message and recipient writes in the thread #36614
Comments
Triggered auto assignment to @trjExpensify ( |
Discussing in thread. |
Self assigning as I am working on very similar issue #22186 and came across this bug while fixing the former. I had a brief look and will handle this |
The error comes from this logic Lines 2518 to 2521 in 8907eef
For a parent message deleted in #admins or user created room, we enter the condition and return |
Nice, so @MonilBhavsar.. confirming this hit prod yesterday and we don't have anyone to pay out for the review, so we can go ahead and close this? |
Yes! Let's close this |
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 reproduction
Reproducible in production?: needs reproduction
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: @rafecolton
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1707847433641419
Action Performed:
Expected Result:
User B should see "deleted message" in the header when in the thread
Actual Result:
Skeleton is loading for ever and also User A is showing as "Hidden" in the LHN
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: