-
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
[$500] LHN last message is not updating after deleting attachment #26564
Comments
Triggered auto assignment to @adelekennedy ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~017f650b305c679ab3 |
Current assignee @adelekennedy is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.LHN last message is not updating after deleting the attachment What is the root cause of that problem?The function What changes do you think we should make in order to solve the problem?We can avoid using
The above condition is safe as In addition, we also need to set the
Further, I am not sure if there is a need to set What alternative solutions did you explore? (Optional) |
@jjcoffee can you review the proposals above? |
This seems like a pretty edgy edge case to me! It requires being signed in as the same user in two tabs, which in itself is a pretty unlikely use case - but then adding on top of that trying to switch between tabs and make actions on one and see the changes on another is just not something I think a normal user would do. I recommend closing unless there's a deeper issue. cc @adelekennedy Additionally, the RCAs proposed so far don't seem to be correct as the behaviour doesn't happen when logged in to a separate account, but |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Let's close this! I love eliminating edge cases |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
LHN should update as well with next previous message
Actual Result:
Not updating
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.62-1
Reproducible in staging?: y
Reproducible in production?: y
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
Kapture.2023-08-25.at.20.30.54.mp4
Recording.1554.mp4
Expensify/Expensify Issue URL:
Issue reported by: @b4s36t4
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692975870405119
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: