[Guides] Chats that are already read show up as unread in LHN

[kevinksullivan]

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. Select focus mode
2. Click into an unread chat
3. Navigate elsewhere

Expected Result:

The chat that is already read shouldn't show in LHN as unread

Actual Result:

The chat is shown as unread several seconds later

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: v1.3.34-1
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

NewDot.Bug.mov

Slack conversation: https://expensify.slack.com/archives/C036S0BVAHH/p1688135931190779

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @MariaHCD (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[melvin-bot]

Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue. cc @thienlnam

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @mananjadhav (Internal)

[MariaHCD]

Not able to 100% reproduce the issue in dev. But I managed to see it with:

1. A (non-high-traffic) account on an IOU report (this is expected, the newest message was a notification that the IOU was paid)

Screen.Recording.2023-07-12.at.1.00.51.PM.mov

2. A moderately high-traffic account (1000 chat reports with 5 report actions each):

Screen.Recording.2023-07-12.at.1.38.07.PM.mov

[MariaHCD]

Not sure if related to #21766 because it seems happens for a non-high-traffic account in dev as well (although not 100% reproducible for me)

Seems like there are two scenarios in #focus mode:

1. In the video attached in the OP, the user's read chats show up as unread when reloading the app
2. In this case, the user views a chat (which should also set it as read) but it shows up as unread again after sometime

[MariaHCD]

More discussions happening here: https://expensify.slack.com/archives/C04JD99283A/p1689202761085489

[MariaHCD]

Update:

• The guide who originally reported the bug doesn't seem to be facing the issue anymore: https://expensify.slack.com/archives/C036S0BVAHH/p1689268396379479?thread_ts=1688135931.190779&cid=C036S0BVAHH. I looked in the deploy checklist for 2023-07-13 here, but couldn't see anything that might've touched on unread messages.
• The issue is being reproduced consistently for contributors@ because this email is intentionally being filtered out when updating the lastRead timestamp: https://expensify.slack.com/archives/C04JD99283A/p1689344967205299?thread_ts=1689202761.085489&cid=C04JD99283A
• We also see this happen (very inconsistently) for IOU reports: https://expensify.slack.com/archives/C04JD99283A/p1689345667761529?thread_ts=1689202761.085489&cid=C04JD99283A

Next steps:

1. Investigate how to fix the issue for contributors@
2. Investigate if this issue affects IOU reports, this issue doesn't seem to be 100% reproducible for IOU reports.
3. Keep an eye out if any guides report the issue again and have them follow these instructions

Co-assigning you @MonilBhavsar! Let me know if I missed anything above.

[MonilBhavsar]

Investigate how to fix the issue for contributors@
Looks like we'll be using a new account to get ignore that condition in code

Sounds good 👍

David thinks this issue is reproducible when using same account on different devices, pointing to unreliable pusher delivery - https://expensify.slack.com/archives/C04JD99283A/p1689375389197839

[sakluger]

@MariaHCD @MonilBhavsar - The Guide [email protected] says that this is still happening for her (Slack thread). Maybe you could use the new V0 Supportal tool to try reproducing in her account? Instructions on using the supportal tool are here: https://stackoverflowteams.com/c/expensify/questions/16975/16976

[MariaHCD]

Latest here: https://expensify.slack.com/archives/C04JD99283A/p1689785584377169?thread_ts=1689724796.767359&cid=C04JD99283A

[MonilBhavsar]

Discussed in slack. Guides are actually facing this issue #17316

[zanyrenney]

Does that mean we should close this out @MonilBhavsar ? Or combine the issues and tackle them in one?

[MonilBhavsar]

I think we can bump the priority of this issue, as no one is experiencing it at the moment. As I mentioned above, guides are experiencing the other similar issue related to unread messages #17316

[melvin-bot]

@mananjadhav @MariaHCD @MonilBhavsar @zanyrenney this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[zanyrenney]

sorry what do you mean bump? do you mean punt or reduce the urgency to weekly? @MonilBhavsar

[MonilBhavsar]

Yes, I did and Melvin updated to daily again. I think we can close this GH as this issue is no longer faced by anyone. Thoughts @kevinksullivan @sakluger

[zanyrenney]

Closing in that case, we can reopen if we get more live cases of this!