Skip to content

[HOLD for payment 2024-07-10] [$500] critical: Chat is not marked as read when receiving a message being in the chat #40152

@m-natarajan

Description

@m-natarajan

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-3
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
Expensify/Expensify Issue URL:
Issue reported by: @iwiznia
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1711638025134599

Action Performed:

  1. Go to any chat
  2. Open another tab or not having the window on focus
  3. Receive a notification for a new message in the chat
  4. Click on the notification and land on the chat
  5. Chat should be marked since message is read
  6. Go to another chat
  7. Again open the chat where the message is received

Expected Result:

In step 4 or in step 6 LHN should be unbold as the message is read

Actual Result:

Still showing as unread, user has to click back to the chat as in step 7 to show as "read"

Workaround:

unknown

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

Chat.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~018e5ebea78782ee33
  • Upwork Job ID: 1778874424236658688
  • Last Price Increase: 2024-07-03
  • Automatic offers:
    • abdulrahuman5196 | Reviewer | 102764320
    • allgandalf | Contributor | 102884646
Issue OwnerCurrent Issue Owner: @dylanexpensify
Issue OwnerCurrent Issue Owner: @dylanexpensify

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHigh Priority

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions