Chat - LHN does not show [Comment deleted] for the user after deleting the message

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Issue was found when executing #4133

Action Performed:

1. Launch the app
2. Log in with any account
3. Send the message
4. Go back to LHN and check the message
5. Back to user you sent message and delete it.

Expected Result:

The LHN shows "[Comment deleted]" for that user

Actual Result:

The LHN doesn't show "[Comment deleted]"

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Android

Version Number: 1.1.16-1
Reproducible in staging?: Yes
Reproducible in production?: No
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Issue was found when executing #4133

Issue reproducible occasionally.

Bug5341146_Screen_Recording_20211122-205501_New_Expensify.mp4

Bug5341146_Screen_Recording_20211122-210144_New_Expensify.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

Triggered auto assignment to @MonilBhavsar (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[Beamanator]

I wonder if this could be related to the change for this issue: #3293

[parasharrajat]

Yeah, Actually, it would have been solved by #3293.

[dklymenk]

Hi, I am the author of the mentioned PR. Thanks for raising the issue, but I can't seem to reproduce it. Is there more to it than just android? Here is video from android on dev mode:

6422.mp4

[MonilBhavsar]

I am also unable to reproduce the issue on Android simulator

[isagoico]

I'm unable to reproduce this on Android on build 1.1.16-6, I think we're good to close it out