Skip to content

Expense - Downloaded PDF receipt on merge distance confirm page cannot be opened #78568

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.2.88-5
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: #78233
Email or phone of affected tester (no customers): sdoijondijdsoijdsosj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Create two Map distance expenses.
  4. Go to Reports > Expenses.
  5. Select both expenses via checkbox.
  6. Click dropdown button > Merge.
  7. Select any merchant > Next.
  8. On confirm page, open the receipt.
  9. Click download button.
  10. Open the downloaded PDF.

Expected Result:

Downloaded PDF receipt will open without issue.

Actual Result:

Downloaded PDF receipt on merge confirm page cannot be opened. Error shows up.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7039057_1767071709029.13.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 Dec 30, 2025
  2. melvin-bot commented on Dec 30, 2025

    @melvin-bot

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

  3. melvin-bot commented on Dec 30, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 30, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 30, 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. hoangzinh commented on Dec 30, 2025

    @hoangzinh
    Contributor

    I think it has same root cause with #78567 (comment)

    cc @youssef-lr

  7. removed
    DeployBlockerIndicates it should block deploying the API
    on Dec 30, 2025
  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 30, 2025
  9. mountiny commented on Dec 30, 2025

    @mountiny
    Contributor

    This is a new feature and minor edge case so demoting and @youssef-lr is handling it shortly

  10. youssef-lr commented on Jan 2, 2026

    @youssef-lr
    Contributor

    I retested this and it's fixed.

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.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions