Skip to content

Report - Track expense deleted from report is displayed with infinite loading on preview. #66836

Closed

Description

@mitarachim

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.1.84-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/test-runs/TR-134/folder/12015305/39317673/797465577
Email or phone of affected tester (no customers): ibellicotest+1376@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 10 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.
Prerequisite 2: Account has a Self DM.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Submit a manual expense.
  4. Navigate to Self DM.
  5. Submit a manual track expense.
  6. Open the just created expense.
  7. Tap on the report field and select the report where the first expense was submitted.
  8. Once the expense was moved, navigate to workspace chat again.
  9. Open the expenses report.
  10. Long tap and select the just moved track expense.
  11. Delete the track expense.
  12. Note that expense disappears from report.
  13. Return to chat. (On Web, using device´s back button)
  14. Note that deleted expense is displayed with infinite loading on report preview.
  15. Note that report preview, still displays a "Review" button.

Expected Result:

Expense deleted from a report, should disappear automatically from report preview in chat.

Actual Result:

Track expense that was moved to a report on a workspace, is displayed with infinite loading on preview after being deleted. Also, report preview still displays a "Review" button, related to the missing merchant error on the deleted expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6894478_1753124019842.Infinite.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jul 22, 2025
  2. melvin-bot commented on Jul 22, 2025

    @melvin-bot

    Triggered auto assignment to @isabelastisser (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.

  3. github-actions commented on Jul 22, 2025

    @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.
  4. melvin-bot commented on Jul 22, 2025

    @melvin-bot

    Triggered auto assignment to @grgia (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. melvin-bot commented on Jul 22, 2025

    @melvin-bot

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

  6. 25 remaining items

  7. grgia commented on Jul 22, 2025

    @grgia
    Contributor

    @Pujan92 @etCoderDysto I believe this blocker was caused by #66054

  8. added and removed on Jul 22, 2025
  9. Pujan92 commented on Jul 22, 2025

    @Pujan92
    Contributor

    I don't think it is related to our PR as it only allows moving iou report without considering deleted transactions. I am also not able to reproduce this issue.

  10. Pujan92 commented on Jul 22, 2025

    @Pujan92
    Contributor
    Screen.Recording.2025-07-22.at.21.57.51.mov
    Simulator.Screen.Recording.-.iPhone.15.Pro.-.2025-07-22.at.21.49.10.mp4
  11. etCoderDysto commented on Jul 22, 2025

    @etCoderDysto
    Contributor

    I am not also able to reproduce this on staging.

    Screen.Recording.2025-07-22.at.8.02.01.in.the.evening.mp4
  12. Pujan92 commented on Jul 22, 2025

    @Pujan92
    Contributor

    @mitarachim may I ask you to retest one more time plz

  13. cristipaval commented on Jul 22, 2025

    @cristipaval
    Contributor

    asked for a retest here

  14. m-natarajan commented on Jul 22, 2025

    @m-natarajan

    Issue is not reproducible. Windows10/Chrome
    build 9.1.84-2

    Recording.3472.mp4
  15. cristipaval commented on Jul 22, 2025

    @cristipaval
    Contributor

    Alright, it looks like #66864 fixed it

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions