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-03-02] [Due for payment 2026-02-27] [$250] Reports - Only the first of several expenses created in a row is highlighted in Reports #83004
Version Number: 9.3.23-2 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#82538 Email or phone of affected tester (no customers):fischer9966+021926+82538c@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: iPhone 16 Pro / 26.3 App Component: Money Requests
Action Performed:
Login to Expensify App with new gmail account
Create new workspace
Navigate to "Reports" and select "Expenses" in filters
Create a manual expense.
Once expense preview is not highlighted anymore, open it.
Close expense
Verify that the expense is not highlighted again
Create a second manual expense
Verify that only the newly created expense is highlighted
Expected Result:
Only the newly created expense is highlighted
Actual Result:
Only the first of several expenses created in a row is highlighted. The second and subsequent expenses are not highlighted. If user leave Reports and return, everything is repeated - only the first expense will be highlighted.
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #82538 - "fix: Expense created while on "Reports", gets highlighted again when opened." by @etCoderDysto (High confidence) Related Issues: #81474 (the issue PR #82538 was trying to fix)
Recommendation: REVERT
PR #82538 introduced a regression while attempting to fix the highlighting behavior. The PR should be reverted to restore proper highlighting for multiple consecutive expense creations.
Labels: Keeping DeployBlockerCash (App deploy is blocked). This is a frontend bug requiring an App PR fix.
Detailed Analysis
Evidence
The bug is reproducible in staging (version 9.3.23-2) but NOT in production
PR #82538 modified src/hooks/useSearchHighlightAndScroll.ts, which controls expense highlighting behavior in the Reports view. The diff shows that the PR moved requestAnimationFrame logic from one effect to another:
Key changes:
Lines 235-253: Effect that resets transactionIDsToHighlight - changed from using requestAnimationFrame + setTimeout to just setTimeout
Lines 264-286: Effect that clears newSearchResultKeys - changed from just setTimeout to requestAnimationFrame + setTimeout
Root Cause
The PR swapped the timing logic between two effects. By adding requestAnimationFrame to the effect that clears newSearchResultKeys (lines 264-286), the clearing of the highlight state is now delayed by an additional animation frame.
When multiple expenses are created in quick succession:
First expense is created → newSearchResultKeys is set with the first expense ID
Highlight appears for the first expense
Second expense is created → The effect tries to set newSearchResultKeys with the second expense ID
The original issue (#81474) that PR #82538 was trying to fix was: "Expense created while on Reports, gets highlighted again when opened." PR #82538 attempted to fix this by ensuring the highlight delay starts after rendering completes. However, this introduced the current regression where subsequent expenses are not highlighted.
changed the title [-][$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/-][+][Due for payment 2026-02-27] [$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/+]on Feb 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.23-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@situchan@mallenexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
changed the title [-][Due for payment 2026-02-27] [$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/-][+][Due for payment 2026-03-02] [Due for payment 2026-02-27] [$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/+]on Feb 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.24-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@situchan@mallenexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Feb 19, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #82538
melvin-bot commentedon Feb 19, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 19, 2026
Triggered auto assignment to @mallenexpensify (
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 commentedon Feb 19, 2026
👋 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:
OSBotify commentedon Feb 19, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #82538 - "fix: Expense created while on "Reports", gets highlighted again when opened." by @etCoderDysto (High confidence)
Related Issues: #81474 (the issue PR #82538 was trying to fix)
Recommendation: REVERT
PR #82538 introduced a regression while attempting to fix the highlighting behavior. The PR should be reverted to restore proper highlighting for multiple consecutive expense creations.
Labels: Keeping
DeployBlockerCash(App deploy is blocked). This is a frontend bug requiring an App PR fix.Detailed Analysis
Evidence
Verification
PR #82538 modified
src/hooks/useSearchHighlightAndScroll.ts, which controls expense highlighting behavior in the Reports view. The diff shows that the PR movedrequestAnimationFramelogic from one effect to another:Key changes:
transactionIDsToHighlight- changed from usingrequestAnimationFrame + setTimeoutto justsetTimeoutnewSearchResultKeys- changed from justsetTimeouttorequestAnimationFrame + setTimeoutRoot Cause
The PR swapped the timing logic between two effects. By adding
requestAnimationFrameto the effect that clearsnewSearchResultKeys(lines 264-286), the clearing of the highlight state is now delayed by an additional animation frame.When multiple expenses are created in quick succession:
newSearchResultKeysis set with the first expense IDnewSearchResultKeyswith the second expense IDnewSearchResultKeysis cleared withrequestAnimationFrame + setTimeout(added in PR fix: Expense created while on "Reports", gets highlighted again when opened. #82538), it takes longer to clear. This timing change causes the secondsetNewSearchResultKeyscall to either be lost or batched incorrectly by ReactThe original issue (#81474) that PR #82538 was trying to fix was: "Expense created while on Reports, gets highlighted again when opened." PR #82538 attempted to fix this by ensuring the highlight delay starts after rendering completes. However, this introduced the current regression where subsequent expenses are not highlighted.
16 remaining items
[-][$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/-][+][Due for payment 2026-02-27] [$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/+]melvin-bot commentedon Feb 20, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.23-3 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-02-27. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Feb 20, 2026
@situchan @mallenexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[-][Due for payment 2026-02-27] [$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/-][+][Due for payment 2026-03-02] [Due for payment 2026-02-27] [$250] Reports - Only the first of several expenses created in a row is highlighted in Reports[/+]melvin-bot commentedon Feb 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.24-3 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-03-02. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Feb 23, 2026
@situchan @mallenexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]