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-01-23] Reports - Empty report is no longer selected after removing expense from report #79614
Version Number: 9.3.2-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#75261 Email or phone of affected tester (no customers):oisndjoisdjniosdiojsio@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Search
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Go to Reports > Reports.
Select the report via checkbox.
Open the report.
Click Report > Remove from report.
Click app back button.
Expected Result:
Empty report should remain selected.
Actual Result:
Empty report is no longer selected after removing expense from report.
👋 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: #75261 - "Can't select an empty report from the Reports > Reports page" by @lorretheboy (High confidence) Related Issues: None
Recommendation: ROLL FORWARD
A revert would undo the ability to select empty reports (the feature this PR added), which would reintroduce issue #70591. The fix is straightforward and localized to the selection logic when reports transition from having transactions to being empty.
PR #75261 introduced the ability to select empty reports from the Reports page. The bug occurs specifically when a report transitions from having transactions to being empty:
User selects a report that has transactions → Selection stored by transaction IDs (e.g., selectedTransactions["transactionID123"])
User removes the last transaction from the report → Report now has 0 transactions
Code checks if the now-empty report should remain selected (lines 459-471 in src/components/Search/index.tsx)
BUG: Line 478-480 checks if reportKey in selectedTransactions, but the selection was stored by transaction IDs, not by reportKey
Empty report is not found in selectedTransactions and loses its selection state
Verification
The bug is reproducible following the exact steps in the issue:
Creating an expense creates a report with 1 transaction
Selecting that report stores the transaction ID in selectedTransactions
Removing the expense makes the report empty
The selection logic fails to maintain selection because it looks for reportKey, not the previous transaction IDs
The previous selection state used transaction IDs as keys
After removal, the code checks for reportKey in selectedTransactions
Since reportKey was never in selectedTransactions (only transaction IDs were), wasReportSelected is false
The report loses its selection state
The fix needs to check if any transactions from the report were previously selected before the report became empty, and if so, convert that to an empty report selection.
QA team rechecked the issue. The behavior is the same on production; however, since it’s not possible to select an empty report on prod, the issue is considered Not Reproducible
changed the title [-]Reports - Empty report is no longer selected after removing expense from report[/-][+][Due for payment 2026-01-23] Reports - Empty report is no longer selected after removing expense from report[/+]on Jan 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.3-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@luacmartins@dylanexpensify 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 Jan 14, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #75261
melvin-bot commentedon Jan 14, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 14, 2026
Triggered auto assignment to @dylanexpensify (
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 Jan 14, 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 Jan 14, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #75261 - "Can't select an empty report from the Reports > Reports page" by @lorretheboy (High confidence)
Related Issues: None
Recommendation: ROLL FORWARD
A revert would undo the ability to select empty reports (the feature this PR added), which would reintroduce issue #70591. The fix is straightforward and localized to the selection logic when reports transition from having transactions to being empty.
Labels: Keeping
DeployBlockerCash(fix requires App PR)📋 Detailed Analysis
Evidence
PR #75261 introduced the ability to select empty reports from the Reports page. The bug occurs specifically when a report transitions from having transactions to being empty:
selectedTransactions["transactionID123"])src/components/Search/index.tsx)reportKey in selectedTransactions, but the selection was stored by transaction IDs, not by reportKeyVerification
The bug is reproducible following the exact steps in the issue:
Root Cause
Lines 474-480 in
src/components/Search/index.tsx:When a report has transactions and becomes empty:
wasReportSelectedis falseThe fix needs to check if any transactions from the report were previously selected before the report became empty, and if so, convert that to an empty report selection.
IuliiaHerets commentedon Jan 15, 2026
QA team rechecked the issue. The behavior is the same on production; however, since it’s not possible to select an empty report on prod, the issue is considered Not Reproducible
Screen.Recording.2026-01-15.at.18.17.02.mp4
[-]Reports - Empty report is no longer selected after removing expense from report[/-][+][Due for payment 2026-01-23] Reports - Empty report is no longer selected after removing expense from report[/+]melvin-bot commentedon Jan 16, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.3-8 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-01-23. 🎊
melvin-bot commentedon Jan 16, 2026
@luacmartins @dylanexpensify 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]