[$1000] "----------New" message removed after two replies.

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

---

Action Performed:

1. Open two web app send message to User A from User B
2. open User B chat from User A you will see green line "New" message
3. reply back to User B (green line "New" message will be removed after one reply)
4. now send message from User B to User A again you will see green line "New" again
5. now reply to User B from User A now this time green line "New" will removed after two replies

Expected Result

Green line "New" message should be remove after one reply

Actual Result:

"--New" message removed after two replies

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?

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

Version Number: 1.2.67-2
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
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:

2023-02-09.14-59-40-1.mp4

Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675938702382709?thread_ts=1675888386.030119&cid=C049HHMV9SM

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01893843251fa388df
• Upwork Job ID: 1625905024362889216
• Last Price Increase: 2023-02-15

[MelvinBot]

Triggered auto assignment to @NicMendonca (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

[NicMendonca]

@kavimuru can you please fill out the platforms check box please?

[kavimuru]

@NicMendonca I was not able to reproduce. Contributor was able to reproduce in all the platforms

[NicMendonca]

@kavimuru okay, thanks! The contributor can still reproduce: https://expensify.slack.com/archives/C049HHMV9SM/p1676470679632749?thread_ts=1675888386.030119&cid=C049HHMV9SM

Trying on my end now!

[NicMendonca]

I can't reproduce this:

[NicMendonca]

Okay I got it actually:

My steps were:

• User A sends User B one message
• User B replies
• User A sends User B two back to back messages
• User B sees all 3 messages as "new", even though they have already seen the first message

[NicMendonca]

Another video from the contributor: https://expensify.slack.com/archives/C049HHMV9SM/p1676471724956199?thread_ts=1675888386.030119&cid=C049HHMV9SM