Unread messages are shown in the LHN whenever a report data is exported to a CSV

[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:
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
Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1719592386443209

Action Performed:

1. Export a report data to a CSV
2. verify the LHN

Expected Result:

These reports should not appear unread in the LHN

Actual Result:

• Exporting to CSV is a report action that we call a “system message”
• Recently implemented a change internally such as all “system messages” are marked as read
• Despite that, every time the team exports report data to a CSV, LHN is showing unread reports as result of the CSV export
• We’ve confirmed that the lastReadTime was correctly set to a time later than system message for the CSV

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

View all open jobs on GitHub

[melvin-bot]

Current assignee @JmillsExpensify is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to @nkuoch (AutoAssignerNewDotQuality)

[m-natarajan]

#44683

[hurali97]

@muttmuure Please assign this to me 👋

[muttmuure]

Ty!

[deetergp]

@hurali97 I suspect this is related to/a duplicate of this GH #44693 so I'd hold at least until that hits production and we do some testing.

[deetergp]

Investigations are still ongoing with the issue this dupes. Will update here when we know more.

[melvin-bot]

@deetergp @JmillsExpensify @hurali97 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!

[puneetlath]

Is this issue different than #44693?

[deetergp]

No, I don't think so. This is a dupe of that issue. Closing…