Scan expense - Receipt is not displayed correctly when details opened from multi expense report

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.2.87-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: https://test-management.browserstack.com/projects/2219752/folder/13176933/test-cases/41237704 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Regression TC Execution Device used: MacBook Air 15.6.1 Chrome App Component: Money Requests

Action Performed:

1. Sign in to ND
2. Navigate to the workspace chat
3. Create a report with two expenses, one of them is scan expense (pdf or image file, not E-receipt)
4. Open the report, open the scan expense and observe the receipt preview

Expected Result:

The receipt is fully visible in the expense details

Actual Result:

The receipt is not fully visible in the expense details. It looks zoomed in, pdf receipt is blurry

Workaround:

Unknown

Platforms:

• [ ] Android: App
• [ ] Android: mWeb Chrome
• [ ] iOS: App
• [ ] iOS: mWeb Safari
• [ ] iOS: mWeb Chrome
• [x] Windows: Chrome
• [ ] MacOS: Chrome / Safari

Screenshots/Videos

https://github.com/user-attachments/assets/b4ea1fdd-e849-4e5c-83d4-bfefb60b248e

Receipts:

Amazon.com - Order 112-6150290-8388252.pdf

View all open jobs on GitHub

[melvin-bot[bot]]

Everybody was OOO, so I assigned 10 random eligible people.

[melvin-bot[bot]]

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

[github-actions[bot]]

:wave: 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.

[melvin-bot[bot]]

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

[izarutskaya]

Different when Staging Server disabled

Production

[izarutskaya]

With Staging server OFF, no receipt preview in expense details. Blank frame MacOS Monterey / Chrome Web v9.2.87-4 PR:78466

https://github.com/user-attachments/assets/4809fda9-96ff-40ca-966b-179874796c25

https://github.com/user-attachments/assets/49fbe269-9edf-4302-a0de-30f1cbd25ce0

https://github.com/user-attachments/assets/cb7171bb-1dc0-460b-bf5a-431782f0aa3e

[situchan]

@izarutskaya that might be because image is staging url while server is pointed to production. I think you should just test staging against staging server, production against production server. No mixes.

[izarutskaya]

We tested with this build https://78466.pr-testing.expensify.com/.

[kavimuru]

Bug is not reproducible.

https://github.com/user-attachments/assets/77d25858-48f8-4c79-8193-78693bec7c83

[mountiny]

No longer repro

[jliexpensify]

We can just close this right @mountiny? It doesn't need to be worked on?

[situchan]

I helped resolving this blocker.

[mountiny]

We can pay $50 to @situchan for help identifying the offending PR and raising the revert

[melvin-bot[bot]]

⚠️ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

[melvin-bot[bot]]

The solution for this issue has been :rocket: deployed to production :rocket: in version 9.2.88-7 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

• https://github.com/Expensify/App/pull/78466

If no regressions arise, payment will be issued on 2026-01-06. :confetti_ball:

For reference, here are some details about the assignees on this issue:

• @situchan requires payment (Needs manual offer from BZ)

[melvin-bot[bot]]

@situchan @jliexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot[bot]]

Job added to Upwork: https://www.upwork.com/jobs/~022006083773144398738

[melvin-bot[bot]]

Current assignee @situchan is eligible for the External assigner, not assigning anyone new.

[jliexpensify]

Sent you an offer @situchan for https://www.upwork.com/jobs/~022006083773144398738

I'll pay as soon as you accept

[jliexpensify]

Bump @situchan to accept

[jliexpensify]

Paid and job closed!