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 2/12/2026] [$250] Reports - Selection mode is displayed, but report not selected, after creating new report #79636
Version Number: 9.3.2.1 Reproducible in staging?: Yes Reproducible in production?: Yes 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):ibellicotest+2250@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Motorola MotoG60 / Android 12 (Hybrid app) App Component: Search
Action Performed:
Prerequisite: Account has at least one workspace.
Open the Expensify app.
Open any workspace chat.
Create a manual expense.
Navigate to "Reports" > "Reports"
Select the just created expense.
Tap on "Create" button and create an empty report.
Tap on the back button on the top left corner to return to "Reports"
Long tap and select the report with the expense created on step 3 again.
Note that selection mode is displayed, but expense is not selected.
Expected Result:
After selecting a report while on "Reports", selection mode should be displayed with a "1 selected" message and the report should be seen automatically selected.
Actual Result:
When selecting a report with an expense while on "Reports" section, after adding a new report, selection mode is displayed, but report is not selected and a "0 selected" message can be seen on dropdown menu.
Please re-state the problem that we are trying to solve in this issue.
When a user creates an empty report, goes back to the Reports list, and long-presses a report to select it, the selection mode is displayed but shows "0 selected" instead of "1 selected". The report is not actually selected.
What is the root cause of that problem?
The root cause is that selectedTransactions is not being cleared when the user navigates away from the Reports list to create a new report.
This ensures that when the user creates a new report and navigates away, any previous selections are cleared, so when they return and long-press a report, it will be properly selected as a fresh selection.
Note: Alternatively, we can clear the selected transaction elsewhere (for example, within the createNewReport function).
What alternative solutions did you explore? (Optional)
Please re-state the problem that we are trying to solve in this issue.
When selecting a report with an expense while on "Reports" section, after adding a new report, selection mode is displayed, but report is not selected and a "0 selected" message can be seen on dropdown menu.
What is the root cause of that problem?
When we navigate to the money request report page, the selection mode is turned off, but the selected transaction isn't cleared. Then it's unselected when we enable the selection mode again.
What changes do you think we should make in order to solve the problem?
Because the selection can be turned off in other pages, we can define onTurnOffSelectionMode callback in useMobileSelectionMode hook to clear the selected transactions when the selection is turned off. This approach ensures the selected transaction is always cleared whenever the selection mode is off.
export default function useMobileSelectionMode(onTurnOffSelectionMode = () => {}) {
const [isSelectionModeEnabled = false] = useOnyx(ONYXKEYS.MOBILE_SELECTION_MODE, {initWithStoredValues: false, canBeMissing: true});
const initialSelectionModeValueRef = useRef(isSelectionModeEnabled);
const prevIsSelectionModeEnabled = usePrevious(isSelectionModeEnabled);
useEffect(() => {
// in case the selection mode is already off at the start, we don't need to turn it off again
if (!initialSelectionModeValueRef.current) {
return;
}
turnOffMobileSelectionMode();
}, []);
useEffect(() => {
if (!prevIsSelectionModeEnabled || isSelectionModeEnabled) {
return;
}
onTurnOffSelectionMode();
}, [prevIsSelectionModeEnabled, isSelectionModeEnabled, onTurnOffSelectionMode]);
return !!isSelectionModeEnabled;
}
What alternative solutions did you explore? (Optional)
We can create an useEffect on SearchPage to clear the selected transactions when the selection mode is turned off.
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
changed the title [-]Reports - Selection mode is displayed, but report not selected, after creating new report[/-][+][$250] Reports - Selection mode is displayed, but report not selected, after creating new report[/+]on Jan 19, 2026
changed the title [-][$250] Reports - Selection mode is displayed, but report not selected, after creating new report[/-][+][Due for Payment 2/12/2026] [$250] Reports - Selection mode is displayed, but report not selected, after creating new report[/+]on Feb 12, 2026
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Prerequisite: Account has at least one workspace.
Open any workspace chat.
Create a manual expense.
Navigate to "Reports" > "Reports"
Select the just created expense.
Tap on "Create" button and create an empty report.
Tap on the back button on the top left corner to return to "Reports"
Long tap and select the report with the expense created on step 3 again.
Verify that the selection mode is displayed and the expense is selected.
Activity
melvin-bot commentedon Jan 15, 2026
Triggered auto assignment to @CortneyOfstad (
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.daledah commentedon Jan 15, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When a user creates an empty report, goes back to the Reports list, and long-presses a report to select it, the selection mode is displayed but shows "0 selected" instead of "1 selected". The report is not actually selected.
What is the root cause of that problem?
The root cause is that
selectedTransactionsis not being cleared when the user navigates away from the Reports list to create a new report.App/src/pages/home/sidebar/FloatingActionButtonAndPopover.tsx
Lines 238 to 254 in 476358b
The issue occurs because:
selectedTransactionsselectedTransactionsis NOT clearedselectedTransactionstoggleTransactionis called which TOGGLES the selection OFF (because it was already selected)If the user long-presses a DIFFERENT report, it shows "2 selected" (the old selection + new one), which confirms the selections are not being cleared.
What changes do you think we should make in order to solve the problem?
Call
clearSelectedTransactions()when navigating away to create a new report inFloatingActionButtonAndPopover.tsx:This ensures that when the user creates a new report and navigates away, any previous selections are cleared, so when they return and long-press a report, it will be properly selected as a fresh selection.
Note: Alternatively, we can clear the selected transaction elsewhere (for example, within the
createNewReportfunction).What alternative solutions did you explore? (Optional)
nkdengineer commentedon Jan 15, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When selecting a report with an expense while on "Reports" section, after adding a new report, selection mode is displayed, but report is not selected and a "0 selected" message can be seen on dropdown menu.
What is the root cause of that problem?
When we navigate to the money request report page, the selection mode is turned off, but the selected transaction isn't cleared. Then it's unselected when we enable the selection mode again.
App/src/components/MoneyReportHeader.tsx
Line 1533 in fb1e667
App/src/components/MoneyReportHeader.tsx
Line 1614 in fb1e667
What changes do you think we should make in order to solve the problem?
Because the selection can be turned off in other pages, we can define
onTurnOffSelectionModecallback inuseMobileSelectionModehook to clear the selected transactions when the selection is turned off. This approach ensures the selected transaction is always cleared whenever the selection mode is off.App/src/hooks/useMobileSelectionMode.ts
Line 6 in fb1e667
App/src/pages/Search/SearchPage.tsx
Line 113 in fb1e667
What alternative solutions did you explore? (Optional)
We can create an
useEffectonSearchPageto clear the selected transactions when the selection mode is turned off.Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
CortneyOfstad commentedon Jan 19, 2026
Getting eyes on this!
[-]Reports - Selection mode is displayed, but report not selected, after creating new report[/-][+][$250] Reports - Selection mode is displayed, but report not selected, after creating new report[/+]melvin-bot commentedon Jan 19, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022013299015552831244
melvin-bot commentedon Jan 19, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (
External)13 remaining items
CortneyOfstad commentedon Feb 12, 2026
PR went to production, but automation did not run for payment — sorry about that!
CortneyOfstad commentedon Feb 12, 2026
@truph01 can you complete the checklist ASAP? Thank you!
[-][$250] Reports - Selection mode is displayed, but report not selected, after creating new report[/-][+][Due for Payment 2/12/2026] [$250] Reports - Selection mode is displayed, but report not selected, after creating new report[/+]truph01 commentedon Feb 12, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Prerequisite: Account has at least one workspace.
Do we agree 👍 or 👎
deetergp commentedon Feb 12, 2026
Checklist looks right to me 👍
CortneyOfstad commentedon Feb 13, 2026
Payment Summary
@nkdengineer — to be paid $250 via NewDot
@truph01 — to be paid $250 via NewDot
Regression Test
https://github.com/Expensify/Expensify/issues/600162
twisterdotcom commentedon Feb 25, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-34a3-ab46-98e2-303772bd4554JmillsExpensify commentedon Apr 5, 2026
$250 approved for @truph01
deltaexecutor123 commentedon May 3, 2026
melvin-bot commentedon May 3, 2026