[HOLD 79756] [$250] Unable to Select Empty Reports for Deletion in Reports > Reports

[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: 9.2.95-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Create an empty report in a workspace chat
2. Navigate to Reports > Reports
3. Locate an empty report
4. Attempt to select the report (checkbox or row selection)

Expected Result:

Empty reports can be selected by clicking the checkbox, User can delete empty reports from the Reports page

Actual Result:

Empty reports cannot be selected

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

2026-01-06_21-52-58.mp4

Recording.2169.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022009221058623083664
• Upwork Job ID: 2009221058623083664
• Last Price Increase: 2026-01-08

Issue Owner

Current Issue Owner: @dominictb

[melvin-bot]

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.

[twinkle-react]

###Proposal

Please re-state the problem that we are trying to solve in this issue.

The issue is in the TransactionGroupListItem component where empty reports are disabled from selection. Users are unable to select empty expense reports for deletion because the checkbox is disabled when the report has no transactions.

###What is the root cause of that problem?
The root cause is that the isDisabledOrEmpty logic currently disables the checkbox for any empty transaction group, including empty expense reports. Specifically, the condition isEmpty && isExpenseReportType is being used to control UI behavior, which unintentionally prevents selection of empty reports.

###What changes do you think we should make in order to solve the problem?
We should modify the isDisabledOrEmpty logic to remove the isEmpty condition when determining whether an expense report is selectable. This allows empty expense reports to be selected while preserving the empty view display logic.

File: src/components/SelectionListWithSections/Search/TransactionGroupListItem.tsx
TransactionGroupListItem.tsx Lines 147-150

const isEmpty = transactions.length === 0; // Currently only the transaction report groups have transactions where the empty view makes sense
const shouldDisplayEmptyView = isEmpty && isExpenseReportType;
const isDisabledOrEmpty = isDisabled; // Remove isEmpty condition to allow selection of empty expense reports

Justification:

• The file owns the selection logic for transaction group items, including expense reports.
• Empty expense reports should be selectable for deletion, so we remove the isEmpty condition from disabling the checkbox.
• This preserves the empty view display logic while allowing selection.
• No Onyx timing or navigation race conditions are introduced as this is purely UI logic.
• The change is minimal and targeted, fixing the root cause at the source of the selection logic.

###What alternative solutions did you explore? (Optional)
N/A

[MobileMage]

Please re-state the problem that we are trying to solve in this issue.

Users cannot select empty reports (reports with no transactions) for deletion in the Reports > Reports view. The checkbox is disabled and long-press selection doesn't work for empty reports.

What is the root cause of that problem?

Empty reports are explicitly excluded from selection in three locations:

1. src/components/SelectionListWithSections/Search/ExpenseReportListItem.tsx:59-62

The checkbox is disabled when the report has no transactions:

const isDisabledCheckbox = useMemo(() => {
    const isEmpty = reportItem.transactions.length === 0;
    return isEmpty ?? reportItem.isDisabled ?? reportItem.isDisabledCheckbox;
}, [reportItem.isDisabled, reportItem.isDisabledCheckbox, reportItem.transactions.length]);

2. src/components/Search/SearchContext.tsx:95

Empty reports are filtered out from the selectedReports array used for bulk actions:

selectedReports = data
    .filter((item) => isMoneyRequestReport(item) && item.transactions.length > 0 && ...)

3. src/components/Search/SearchList/index.tsx:311-314

Long press is disabled for empty expense reports (mobile selection):

// disable long press for empty expense reports
if ('transactions' in item && item.transactions.length === 0 && !groupBy) {
    return;
}

What changes do you think we should make in order to solve the problem?

1. ExpenseReportListItem.tsx - Remove the isEmpty check:

const isDisabledCheckbox = useMemo(() => {
    return reportItem.isDisabled ?? reportItem.isDisabledCheckbox ?? false;
}, [reportItem.isDisabled, reportItem.isDisabledCheckbox]);

2. SearchContext.tsx:95 - Remove the transactions.length > 0 filter:

selectedReports = data
    .filter((item) => isMoneyRequestReport(item) && item.transactions.every(({keyForList}) => selectedTransactions[keyForList]?.isSelected))

Note: For empty reports, every() on an empty array returns true, so they will correctly pass the filter when selected.

3. SearchList/index.tsx:311-314 - Remove the empty report long-press block:

// Remove these lines:
// if ('transactions' in item && item.transactions.length === 0 && !groupBy) {
//     return;
// }

What alternative solutions did you explore? (Optional)

N/A

[dmkt9]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Empty reports cannot be selected

What is the root cause of that problem?

• Reports cannot be selected because we disable them here.
  

  App/src/components/SelectionListWithSections/Search/ExpenseReportListItem.tsx

  Lines 62 to 63 in f330976

  	const isEmpty = reportItem.transactions.length === 0;
  	return isEmpty ?? reportItem.isDisabled ?? reportItem.isDisabledCheckbox;

• The "Select all" checkbox will also not work if there are no transactions.
  

  App/src/components/Search/SearchList/index.tsx

  Lines 195 to 199 in f330976

  	if (groupBy || type === CONST.SEARCH.DATA_TYPES.EXPENSE_REPORT) {
  	if (!isTransactionGroupListItemArray(data)) {
  	return data;
  	}
  	return data.flatMap((item) => item.transactions);

• Selection is currently based only on transactions.
  

  App/src/components/Search/index.tsx

  Lines 934 to 945 in f330976

  	setSelectedTransactions(
  	Object.fromEntries(
  	(filteredData as TransactionListItemType[])
  	.filter((t) => !isTransactionPendingDelete(t))
  	.map((transactionItem) => {
  	const itemTransaction = searchResults?.data?.[`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionItem.transactionID}`] as OnyxEntry<Transaction>;
  	const originalItemTransaction = searchResults?.data?.[`${ONYXKEYS.COLLECTION.TRANSACTION}${itemTransaction?.comment?.originalTransactionID}`];
  	return mapTransactionItemToSelectedEntry(transactionItem, itemTransaction, originalItemTransaction, email ?? '', outstandingReportsByPolicyID);
  	}),
  	),
  	filteredData,
  	);

  
  

  App/src/components/Search/index.tsx

  Lines 692 to 706 in f330976

  	setSelectedTransactions(
  	{
  	...selectedTransactions,
  	...Object.fromEntries(
  	currentTransactions
  	.filter((t) => !isTransactionPendingDelete(t))
  	.map((transactionItem) => {
  	const itemTransaction = searchResults?.data?.[`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionItem.transactionID}`] as OnyxEntry<Transaction>;
  	const originalItemTransaction = searchResults?.data?.[`${ONYXKEYS.COLLECTION.TRANSACTION}${itemTransaction?.comment?.originalTransactionID}`];
  	return mapTransactionItemToSelectedEntry(transactionItem, itemTransaction, originalItemTransaction, email ?? '', outstandingReportsByPolicyID);
  	}),
  	),
  	},
  	filteredData,
  	);

What changes do you think we should make in order to solve the problem?

• To allow selection, we need to remove the disable conditions for empty reports.
  

  App/src/components/SelectionListWithSections/Search/ExpenseReportListItem.tsx

  Lines 62 to 63 in f330976

  	const isEmpty = reportItem.transactions.length === 0;
  	return isEmpty ?? reportItem.isDisabled ?? reportItem.isDisabledCheckbox;

  
  

  App/src/components/Search/SearchList/index.tsx

  Line 475 in f330976

  disabled={flattenedItems.length === 0}

• We should implement a state such as selectedEmptyReport, which has a role and implementation similar to selectedTransactions, and is used in cases involving empty reports.
  

  App/src/components/Search/SearchContext.tsx

  Line 77 in f330976

  const setSelectedTransactions: SearchContextProps['setSelectedTransactions'] = useCallback((selectedTransactions, data = []) => {

What alternative solutions did you explore? (Optional)

N/A

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022009221058623083664

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @dominictb (External)

[melvin-bot]

@dominictb Huh... This is 4 days overdue. Who can take care of this?