Skip to content

[Merge] Expense - When merging with failed scan expense, receipt is missing, Amount shows Scanning #78206

Closed

Description

@jponikarchuk

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.85-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #73248
Email or phone of affected tester (no customers): jsodjsodijsojdsij1@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Bug 1:

Precondition:

  • Account has self DM.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Create a manual expense.
  4. Create a scan expense with invalid receipt that will fail the scan.
  5. Wait for scan to fail.
  6. Open the MANUAL expense.
  7. Click More > Merge.
  8. Select the scan expense > Continue.
  9. Reach the confirm page.

Bug 2:

Precondition:

  • Account has self DM.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Create a manual expense.
  4. Create a scan expense with invalid receipt that will fail the scan.
  5. Wait for scan to fail.
  6. Open the FAILED SCAN expense.
  7. Click More > Merge.
  8. Select the manual expense > Continue.
  9. Reach the confirm page.

Expected Result:

Bug 1: Receipt from the scan expense will appear on the confirm page.
Bug 2: Amount field will show the amount from the manual expense.

Actual Result:

Bug 1: Receipt from the scan expense does not appear on the confirm page.
Bug 2: Amount field shows Scanning.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7034444_1766242368759.Bug_1.mp4
Bug7034444_1766242368757.Bug_2.2.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.
    on Dec 20, 2025
  2. melvin-bot commented on Dec 20, 2025

    @melvin-bot

    Triggered auto assignment to @RachCHopkins (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. melvin-bot commented on Dec 20, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 20, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 20, 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.
  6. changed the title [-]Expense - When merging with failed scan expense, receipt is not shown on confirm page[/-] [+]Expense - When merging with failed scan expense, receipt is missing, Amount shows Scanning[/+] on Dec 20, 2025
  7. changed the title [-]Expense - When merging with failed scan expense, receipt is missing, Amount shows Scanning[/-] [+][Merge] Expense - When merging with failed scan expense, receipt is missing, Amount shows Scanning[/+] on Dec 20, 2025
  8. added a commit that references this issue on Dec 21, 2025
    46ee13a
  9. m-natarajan commented on Dec 21, 2025

    @m-natarajan

    Not repro on Bug 1 and Bug 2, Windows 11 / Chrome, v9.2.85-1

    scan.mp4
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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions