[$500] Thread - Message sent after returning from thread is not shown after refreshing the page

[kbecciv]

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: 1.4.62-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #39454
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to chat.
3. Send a message.
4. Right click on the message > Reply in thread.
5. Click on the header subtitle.
6. Send a message back in the main chat.
7. Refresh the page.

Expected Result:

The message sent in Step 6 will appear in the chat history.

Actual Result:

The message sent in Step 6 does not appear in the chat history after refreshing the page.

Workaround:

n/a

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6444996_1712777240325.20240411_032158.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~019444184000784869
• Upwork Job ID: 1780314828568719360
• Last Price Increase: 2024-04-16

[melvin-bot]

Triggered auto assignment to @stitesExpensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[kbecciv]

We think that this bug might be related to #wave-collect - Release 1

[github-actions]

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

[Julesssss]

Possibly introduced by this PR

[stitesExpensify]

@kbecciv can you re-test this? I'm not able to reproduce