You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-25] Mark the revealed Inbox report read after the tap paints #106860
The Inbox tab is preloaded in the background, and useMarkAsRead holds the mark-as-read of the open report until the tab is shown. On the tap that shows it, the report is marked read inside the same commit. That write recomputes the derived report attributes and sorted actions and re-sorts the LHN, all before the sidebar finishes its first layout, which is where ManualNavigateToInboxTab ends. With window focus it even runs twice, once from the initial pass and once from the report-change pass.
Lets keep the read but hold it until the main thread is idle (requestIdleCallback, 1s timeout) when the tap on the Inbox tab is what reveals the report. All of it lives in a new hook, useMarkReadAfterReveal. useMarkAsRead only routes its two reveal reads through it and cancels a held read from its other read paths. Every other read is unchanged, including the reveal of a wide submit pre-mount. To keep the outcome the same as an immediate read.
changed the title [-]Mark the revealed Inbox report read after the tap paints[/-][+][Due for payment 2026-11-25] Mark the revealed Inbox report read after the tap paints[/+]on Nov 18, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.41-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
expensify-chore-bot commentedon Nov 18, 2026
@DylanDylann Eep! 4 days overdue now. Issues have feelings too...
[-]Mark the revealed Inbox report read after the tap paints[/-][+][Due for payment 2026-11-25] Mark the revealed Inbox report read after the tap paints[/+]melvin-bot commentedon Nov 18, 2026
@DylanDylann
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.41-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-11-25. 🎊