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-10-30] Android - Expense - Unable to enter selection mode after switching to table view #103389
Version Number: 9.5.5-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:#103121 Email or phone of affected tester (no customers):[email protected] Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Samsung Galaxy S25 FE / Android 16 App Component: Money Requests
Action Performed:
Launch Expensify app.
Go to workspace chat.
Create an expense.
Open the report.
Tap More > Switch to table view.
Long tap on the expense row > Select.
Expected Result:
App will enter selection mode after switching to table view.
Actual Result:
App cannot enter selection mode after switching to table view.
👋 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.
Root Cause: That PR lets a one-expense report render as a table, so you can long-press a row and tap Select. But an older check in MoneyReportHeader.tsx:145-152 turns selection mode off whenever a report has one expense or none. Selection mode turns on, the header re-renders, sees one expense, and turns it off right away.
Recommendation: Fix forward rather than revert. In MoneyReportHeader.tsx, use the PR's existing useSingleExpenseReportView hook so one expense is enough when the user picked the table view:
Add a case to tests/ui/components/MoneyReportHeaderSelectionModeTest.tsx: saved view is table, report has one expense, selection mode stays on. If the fix can't land quickly, revert the PR.
Investigation details
Line references use the current staging tip, b95bb6bb.
The PR makes shouldDisplayReportTableView return true for one-expense reports when the user picks the table view: MoneyRequestReportUtils.ts:172-177.
The header check (visibleTransactions.length <= 1) existed before this release. It assumed a one-expense report could never be in table view. The PR broke that assumption but did not change the header.
Scope: The check only runs on narrow layouts, and long-press only works on small screens. iOS and mobile web are likely affected too. Wide layouts are not.
Other PRs in the release: I checked all 49 PRs in Deploy Checklist: New Expensify 2026-10-07. No other PR changes table-view or one-expense behavior. No other PR touches MoneyReportHeader.tsx, the selection-mode hooks, or the long-press menu.
changed the title [-]Android - Expense - Unable to enter selection mode after switching to table view[/-][+][Due for payment 2026-10-30] Android - Expense - Unable to enter selection mode after switching to table view[/+]on Oct 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.18-1 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-10-30. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
applause-bot commentedon Oct 7, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/ad70445b3cf6419a8ad6e48bfd83690c34c08acae0aff8988b2e3e6b60305bf5
melvin-bot commentedon Oct 7, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #103121
melvin-bot commentedon Oct 7, 2026
@Beamanator @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #103121
melvin-bot commentedon Oct 7, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 7, 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:
MelvinBot commentedon Oct 7, 2026
Deploy Blocker Analysis
Causing PR: Add a More menu option to switch single-expense reports between expense view and table view (high confidence)
Root Cause: That PR lets a one-expense report render as a table, so you can long-press a row and tap Select. But an older check in
MoneyReportHeader.tsx:145-152turns selection mode off whenever a report has one expense or none. Selection mode turns on, the header re-renders, sees one expense, and turns it off right away.Recommendation: Fix forward rather than revert. In
MoneyReportHeader.tsx, use the PR's existinguseSingleExpenseReportViewhook so one expense is enough when the user picked the table view:Add a case to
tests/ui/components/MoneyReportHeaderSelectionModeTest.tsx: saved view istable, report has one expense, selection mode stays on. If the fix can't land quickly, revert the PR.Investigation details
Line references use the current
stagingtip,b95bb6bb.shouldDisplayReportTableViewreturn true for one-expense reports when the user picks the table view:MoneyRequestReportUtils.ts:172-177.turnOnMobileSelectionMode():MoneyRequestReportTransactionLongPressModal.tsx:58-63.visibleTransactions.length <= 1) existed before this release. It assumed a one-expense report could never be in table view. The PR broke that assumption but did not change the header.Scope: The check only runs on narrow layouts, and long-press only works on small screens. iOS and mobile web are likely affected too. Wide layouts are not.
Other PRs in the release: I checked all 49 PRs in Deploy Checklist: New Expensify 2026-10-07. No other PR changes table-view or one-expense behavior. No other PR touches
MoneyReportHeader.tsx, the selection-mode hooks, or the long-press menu.view run
melvin-bot commentedon Oct 7, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Oct 7, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
19 remaining items
melvin-bot commentedon Oct 21, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
mitarachim commentedon Oct 21, 2026
Deploy Blocker #104657 was identified to be related to the PR #103703 that attempted to fix this issue.
melvin-bot commentedon Oct 21, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Oct 22, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
jponikarchuk commentedon Oct 22, 2026
Deploy Blocker #104676 was identified to be related to the PR #103703 that attempted to fix this issue.
jponikarchuk commentedon Oct 22, 2026
Deploy Blocker #104678 was identified to be related to the PR #103703 that attempted to fix this issue.
jponikarchuk commentedon Oct 22, 2026
Deploy Blocker #104681 was identified to be related to the PR #103703 that attempted to fix this issue.
melvin-bot commentedon Oct 22, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
jponikarchuk commentedon Oct 22, 2026
Deploy Blocker #104682 was identified to be related to the PR #103703 that attempted to fix this issue.
melvin-bot commentedon Oct 22, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-]Android - Expense - Unable to enter selection mode after switching to table view[/-][+][Due for payment 2026-10-30] Android - Expense - Unable to enter selection mode after switching to table view[/+]melvin-bot commentedon Oct 23, 2026
@daledah
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.18-1 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-10-30. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]. If no checklist is needed for this issue, you can click: [no checklist button]