Web - Chat - Read messages in open chat get "New" marker after page refresh

[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!

---

Action Performed:

1. Go to https://staging.new.expensify.com/
   and login, account A on device 1, account B on device 2
2. Create a chat between A and B
3. On device 1 keep chat between A and B open
4. On device 2 send messages to account A
5. Message are received on device 1 and not displayed as new as chat is open.
6. On device 1 refresh the page

Expected Result:

Last messages should not have "New tag" after page refresh as they didn't have before

Actual Result:

Last messages are displayed as "New", however they did not have this tag before page refresh.

Workaround:

Unknown

Platforms:

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

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

Version Number: 1.2.80.0

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

Bug5968641_video_05-1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~011b423a06e75307f4
• Upwork Job ID: 1638333471730647040
• Last Price Increase: 2023-03-22

[MelvinBot]

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

[MelvinBot]

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

[MelvinBot]

@johncschuster Eep! 4 days overdue now. Issues have feelings too...

[MelvinBot]

@johncschuster Still overdue 6 days?! Let's take care of this!

[MelvinBot]

@johncschuster 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

[MelvinBot]

@johncschuster 12 days overdue now... This issue's end is nigh!

[hayata-suenaga]

I was able to repro. I'll assign myself.