Skip to content

[Due for payment 2026-10-30] Android - Report - Unable to move expense to a different report while on table view. #104678

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.16-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: #103703
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: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has a workspace.

  1. Open the Expensify app.
  2. Navigate to workspace chat.
  3. Create a manual expense.
  4. Open the just created expense.
  5. Tap on "More" > "Switch to table view"
  6. Long tap and select the just created expense.
  7. Tap on "Dropdown menu" > "Move to report" > "Create Report"
  8. Note that no action is triggered after tapping "Create Report"
  9. Tap on "Remove from report"
  10. Note that no action is triggered.

Expected Result:

User should be able to move an expense to a new report or remove it from the actual report while on table view.

Actual Result:

User is unable to move expense to a new report or remove it from the actual one while in 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

Bug7292681_1792624319466.View.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7292681

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 22, 2026
  2. applause-bot commented on Oct 22, 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/8e7621eaaa118b3cb831ace9af65dcca215cb939d318d06d5a7111769791a867

  3. melvin-bot commented on Oct 22, 2026

    @melvin-bot

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

  4. github-actions commented on Oct 22, 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.
  5. melvin-bot commented on Oct 22, 2026

    @melvin-bot

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

  6. melvin-bot commented on Oct 22, 2026

    @melvin-bot

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

  7. MelvinBot commented on Oct 22, 2026

    @MelvinBot
    Contributor

    Deploy Blocker Analysis

    Cause (high confidence): Reapply "Add a More menu option to switch single-expense reports between expense view and table view". When the "Move expenses" page opens on a narrow screen, an effect clears the selection. The page then has no expense, so "Create report" and "Remove from report" do nothing.

    Recommendation: revert. Merge the approved [CP Staging] Revert "Reapply "Add a More menu option to switch single-expense reports between expense view and table view"". PR 103703 is linked to several other open blockers on this checklist, so a one-line fix would not clear them all.

    How it breaks
    1. In table view, a single-expense report still passes its raw transaction thread ID through MoneyReportTransactionThreadContext.tsx:43. A table-view-aware version exists in useTransactionThreadReportID.ts:33-37, but the context does not use it.
    2. MoneyReportHeaderActions/index.tsx:65-71 clears the selection on mount whenever that ID is set. The PR added the correct isTransactionThread flag at line 63, but the effect does not use it.
    3. On narrow screens, selection mode replaces the header actions with a "Select multiple" title (MoneyReportHeader.tsx:147-170). When the move page opens, the report loses focus, the actions remount, and the effect clears the selection. Wide screens never remount this component.
    4. The move page opens without a transaction ID (useSelectedTransactionsActions.ts:545-548) and reads only the selection (DynamicIOURequestEditReport.tsx:62-63). With an empty list:

    Other candidates: None of the other PRs on the Deploy Checklist: New Expensify 2026-10-21 touch the selection-clearing effect or the move page.

    Same root cause: Expense - Selection mode is cleared after changing to table view and resizing. Resizing remounts the same component.

    If the feature is reapplied: gate the effect on isTransactionThread instead of transactionThreadReportID. Better still, have the context return the table-view-aware ID by default.


    view run

  8. m-natarajan commented on Oct 22, 2026

    @m-natarajan

    PR reverted and feature "Switch to table view." not available. Samsung Galaxy A40/Android 11/Build 9.5.16-1

    MicrosoftTeams-video.44.mp4
  9. Beamanator commented on Oct 22, 2026

    @Beamanator
    Contributor

    thanks! closing!

  10. changed the title [-]Android - Report - Unable to move expense to a different report while on table view.[/-] [+][Due for payment 2026-10-30] Android - Report - Unable to move expense to a different report while on table view.[/+] on Oct 23, 2026
  11. 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