mWeb- Conversation- A green line appears for a second and disappears on receiving messages

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Go to https://staging.new.expensify.com/
2. User A: Tap on a report
3. Send a message to user B
4. Open user B account
5. Tap the bold message received from user A
6. Send some messages and note conversation page of user A

Expected Result:

A green line must not appears for a second and disappears on receiving messages from user B.

Actual Result:

A green line appears for a second and disappears on receiving messages from user B.

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.73-0

Reproducible in staging?: Y

Reproducible in production?: Y

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

Bug6211406_userb.mp4

Bug6211406_usera.mp4

Bug6211406_Android.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause-Internal Team

Slack conversation: @

View all open jobs on GitHub

[melvin-bot]

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

[mallenexpensify]

It's happening on iOS too (but not desktop). Asking for design feedback
https://expensify.slack.com/archives/C01GTK53T8Q/p1695792469990699

RPReplay_Final1695792150.MP4

[melvin-bot]

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

[mallenexpensify]

Checking on here
https://expensify.slack.com/archives/C01GTK53T8Q/p1696247959483009?thread_ts=1695792469.990699&cid=C01GTK53T8Q

[mallenexpensify]

Putting on hold pending
#23171
and
#25935

[mallenexpensify]

On hold

[mallenexpensify]

Still on hold, the PR should have been reviewed yesterday

• [HOLD for payment 2023-11-29] [Redesign Unread Markers] Fix unread markers and migrate logic to ReportActionsList component #23171 (comment)

[mallenexpensify]

HOld, other issue is slowly moving along
#23171 (comment)

[mallenexpensify]

STill open

• [HOLD for payment 2023-11-29] [Redesign Unread Markers] Fix unread markers and migrate logic to ReportActionsList component #23171 (comment)

[mallenexpensify]

^ Still open

[mallenexpensify]

Still holding, shouldn't be long

[mallenexpensify]

Hold

[mallenexpensify]

Holding....

[mallenexpensify]

Closing, not reproducible on iOS web, latest version

IMG_0970.MOV