Skip to content

[Due for payment 2025-11-26] [$250] Multi scan - Transaction details appear twice and broken after deleting one of the expenses #72075

@mitarachim

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.2.27-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1184/folder/13177049/49475610/940179685
Email or phone of affected tester (no customers): jsdoijnsojsonidjsij@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM.
  3. Click + > Create expense > Scan.
  4. Upload a photo.
  5. On confirm page, click RHP back button.
  6. Upload a photo.
  7. On confirm page, click Create 2 expenses.
  8. Open the expense report.
  9. Open any expense row.
  10. Click More > Delete.
  11. After deleting the expense, scroll up the expense report.

Expected Result:

The expense report will not show the transaction details twice after deleting one of the expenses.

Actual Result:

The expense report shows the transaction details twice after deleting one of the expenses. The duplicate view also looks broken.

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

Bug6968276_1759913872607.Screen_Recording_2025-10-08_at_16.52.19.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021977847568048893670
  • Upwork Job ID: 1977847568048893670
  • Last Price Increase: 2025-10-13
Issue OwnerCurrent Issue Owner: @RachCHopkins

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions