Mark as unread appears on message that are not new

@oleksandr-pantsyr

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:

Log in and open the chat with User A and User B
User B sends a message to User A
User A sends quickly a message to User B before User B's message is not displayed on chat

Expected Result:

Mark as unread should not appear on User A's message. It's not a new message because it's from User A

Actual Result:

Mark as unread appears on User A's message

Workaround:

Unknown

Platforms:

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

Version Number: 1.3.55-7

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

2023-08-09_23-07-58.mp4

Recording.2937.mp4

Expensify/Expensify Issue URL:

Issue reported by: @oleksandr-pantsyr

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691609809199069

View all open jobs on GitHub

@slafortune

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

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

Should be fixed after #18637 hits staging!

@allroundexperts

Hi @allroundexperts
Did you check the video in detail? The video issue is different from #18637 issue.
Which case of 18637 will fix this issue?

@slafortune

Hi @slafortune I don't think the issue will be fixed even if #18637 is fixed.
Could you please check again?

@allroundexperts

Hi @allroundexperts @slafortune
I've reviewed #18637. but I don't think 18637 will fix current issue.
Which case of 18637 will fix this issue? When you are available, please let me know.

Navigation Menu

Repository navigation

Mark as unread appears on message that are not new #25533

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Bug0 Triage Checklist (Main S/O)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Mark as unread appears on message that are not new #25533

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Activity

melvin-bot commented on Aug 19, 2023

melvin-bot commented on Aug 19, 2023

Bug0 Triage Checklist (Main S/O)

allroundexperts commented on Aug 19, 2023

oleksandr-pantsyr commented on Aug 22, 2023

oleksandr-pantsyr commented on Aug 22, 2023

oleksandr-pantsyr commented on Aug 23, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions