Expense - New message marker above "exported to CSV" does not disappear after reopening report

[mitarachim]

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: 9.1.76-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp #64859
Email or phone of affected tester (no customers): sdkmspksdpmosp@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.expensify.com
2. Go to workspace chat.
3. Submit two expenses to the workspace chat.
4. Open the expense report.
5. Click More > Export > Basic export.
6. Go back to main workspace chat.
7. Open the expense report.
8. New message marker appears above "exported to CSV" message.
9. Go back to main workspace chat.
10. Reopen the expense report.

Expected Result:

New message marker will disappear after reopning the expense report.

Actual Result:

New message marker above "exported to CSV" message does not disappear after reopening expense report.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6877841_1751619163633.20250704_164648.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @MarioExpensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[BlameGPT]

Possible culprit PRs for this issue

• Fix: New message marker is not displayed on the first message in expense report #64859: PR 64859 directly modified MoneyRequestReportActionsList logic for positioning the new-message marker, so it could break the marker’s clearing behaviour after reopening a report.
• LHN doesn't show the message sent or the system message #64733: PR 64733 altered OptionsListUtils message retrieval for expense reports, which may interfere with unread/read calculations that hide the new-message marker.

If not above, check these

• Refactor usages of useOnyx to use the App wrapper #64746: Large refactor swapped useOnyx implementations across components including ReportActionsList and ReportActionsView, which drive the new-message marker clearing logic, so state updates may no longer trigger and the marker persists after reopening a report.