Chat - Message received after attachment isn't displayed in LHN until reply is sent and deleted

[lanitochka17]

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:

1. Go to staging.new.expensify.com or open Expensify App on two devices as user A and user B
2. User A open chat with user B
3. User A send attachment (image or PDF) to user B
4. User B send text message to user A
5. === (see expected / actual result) ===
6. User A sends a reply to this message and then deletes this reply
7. Message from step 4 is displayed in LHN

Expected Result:

5. User A receives a message and this message is displayed in LHN

Actual Result:

5. User A receives a message but this message is NOT displayed in LHN

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.41.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

Bug6128733_No-last-message-in-LHN.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

[melvin-bot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[eh2077]

This looks like a regression of #21780

[stephanieelliott]

Thanks @eh2077, made a note on the corresponding issue as well.

[stephanieelliott]

Hey @eh2077 Is there a PR for this yet?

[eh2077]

@stephanieelliott I think the contributor or the C+ will submit a PR to fix this. They'll update in the linked original issue.