You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expense - Downloaded PDF receipt on merge distance confirm page cannot be opened #78568
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:
Go to staging.new.expensify.com
Go to self DM.
Create two Map distance expenses.
Go to Reports > Expenses.
Select both expenses via checkbox.
Click dropdown button > Merge.
Select any merchant > Next.
On confirm page, open the receipt.
Click download button.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Dec 30, 2025
You have been assigned to this deploy blocker because you recently merged this PR: #78233
melvin-bot commentedon Dec 30, 2025
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Dec 30, 2025
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.github-actions commentedon Dec 30, 2025
👋 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:
hoangzinh commentedon Dec 30, 2025
I think it has same root cause with #78567 (comment)
cc @youssef-lr
mountiny commentedon Dec 30, 2025
This is a new feature and minor edge case so demoting and @youssef-lr is handling it shortly
youssef-lr commentedon Jan 2, 2026
I retested this and it's fixed.