Skip to content

[Due for payment 2026-10-30] Android - Expense - Unable to enter selection mode after switching to table view #103389

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


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:

  1. Launch Expensify app.
  2. Go to workspace chat.
  3. Create an expense.
  4. Open the report.
  5. Tap More > Switch to table view.
  6. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7280477_1791403789873.Screen_Recording_20261008_040015_Expensify.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Nathan Lemma
Bug ID: 7280477

Issue OwnerCurrent Issue Owner: @daledah

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 7, 2026
  2. applause-bot commented on Oct 7, 2026

    @applause-bot
    Author

    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

  3. melvin-bot commented on Oct 7, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #103121

  4. melvin-bot commented on Oct 7, 2026

    @melvin-bot

    @Beamanator @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #103121

  5. melvin-bot commented on Oct 7, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. github-actions commented on Oct 7, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  7. MelvinBot commented on Oct 7, 2026

    @MelvinBot
    Contributor

    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-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:

    const {shouldUseTableViewForSingleExpense} = useSingleExpenseReportView();
    // ...
    const minTransactionsForSelection = shouldUseTableViewForSingleExpense ? 1 : 2;
    if (visibleTransactions.length < minTransactionsForSelection) {
        turnOffMobileSelectionMode();
    }

    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.

    1. The PR makes shouldDisplayReportTableView return true for one-expense reports when the user picks the table view: MoneyRequestReportUtils.ts:172-177.
    2. Tapping Select in the long-press menu calls turnOnMobileSelectionMode(): MoneyRequestReportTransactionLongPressModal.tsx:58-63.
    3. 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.


    view run

  8. melvin-bot commented on Oct 7, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  9. melvin-bot commented on Oct 7, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  10. 19 remaining items

  11. melvin-bot commented on Oct 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  12. mitarachim commented on Oct 21, 2026

    @mitarachim

    Deploy Blocker #104657 was identified to be related to the PR #103703 that attempted to fix this issue.

  13. melvin-bot commented on Oct 21, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  14. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  15. jponikarchuk commented on Oct 22, 2026

    @jponikarchuk

    Deploy Blocker #104676 was identified to be related to the PR #103703 that attempted to fix this issue.

  16. jponikarchuk commented on Oct 22, 2026

    @jponikarchuk

    Deploy Blocker #104678 was identified to be related to the PR #103703 that attempted to fix this issue.

  17. jponikarchuk commented on Oct 22, 2026

    @jponikarchuk

    Deploy Blocker #104681 was identified to be related to the PR #103703 that attempted to fix this issue.

  18. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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. jponikarchuk commented on Oct 22, 2026

    @jponikarchuk

    Deploy Blocker #104682 was identified to be related to the PR #103703 that attempted to fix this issue.

  20. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  21. 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
  22. melvin-bot commented on Oct 23, 2026

    @melvin-bot

    @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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions