Show thumbnail preview while receipt image loads

[sosek108]

Explanation of Change

When a receipt image is loading, the app previously showed only a spinner. This PR renders a low-resolution thumbnail (thumbnail320) as a placeholder while the full-resolution image loads. The thumbnail itself shows a spinner until it is ready, then the full image replaces it cleanly. If no thumbnail is available the existing spinner-only behavior is preserved.

Three files changed:

• ImageWithLoading: accepts a new thumbnail320 prop and, when loading, overlays an Image using StyleSheet.absoluteFill with that URI; the spinner is only shown while the thumbnail itself is still loading.
• ReceiptImage: threads thumbnail320 through to ImageWithLoading.
• ReportActionItemImage: derives thumbnail320Source from getThumbnailAndImageURIs (skipping local files) and passes it to both ReceiptImage call sites.

Fixed Issues

$ #85875
PROPOSAL:

Tests

Prequisities: You should start testing on freshly logged in account and the best experience should be in incognito mode.

1. Go to Spend page -> Transactions
2. Open one of Transaction with receipt
3. Observe if low res image is present for the moment a target image is loaded

Note: this fix aims primarily to improve performance for desktop web. It adds the functionality to iOS and Android platform but due to other issues (not related to the fix) the performance gain is not visible. These two issues one and two will be visible while testing.

Offline tests

N/A

QA Steps

Same as tests

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

android_final.mov

new (May 21)

Nagranie.z.ekranu.2026-05-21.o.08.54.50.mov

Android: mWeb Chrome

Nagranie.z.ekranu.2026-05-5.o.13.59.07.mov

iOS: Native

Nagranie.z.ekranu.2026-04-29.o.13.38.45.mov

new (May 21)

Nagranie.z.ekranu.2026-05-21.o.08.45.54.mov

iOS: mWeb Safari

Nagranie.z.ekranu.2026-05-5.o.13.56.03.mov

MacOS: Chrome / Safari

web_final.mov

[melvin-bot]

@Eskalifer1 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[Eskalifer1]

Hi, i will review it today!

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/components/ImageWithLoading.tsx	74.28% <100.00%> (+1.55%)	⬆️
src/components/ImageWithSizeCalculation.tsx	100.00% <ø> (ø)
src/components/ReceiptImage/index.tsx	72.09% <ø> (ø)
...ponents/ReportActionItem/ReportActionItemImage.tsx	68.96% <100.00%> (+1.69%)	⬆️
src/components/ThumbnailImage.tsx	92.10% <ø> (ø)
... and 12 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e51a2698d4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[Eskalifer1]

Hi @sosek108, Can you let me know if this PR is ready for review?

If not, please bump me when it’s ready, since it doesn’t seem fully ready yet — I see that not all comments have been addressed, there are no platform-specific videos, and there’s an ESLint error.

If it’s ready for review, I’ll get back to it today. Just let me know :)

[marcaaron]

Changes LGTM. The PR to fix "OpenApp does not provide thumbnail data for newly-uploaded receipts" is on staging now if we want to test against there to see if that bug has been solved now.

[sosek108]

@Eskalifer1 I fixed CI issues. You can review now

edit: I spotted some error on iOS today. So

[sosek108]

@Eskalifer1

I've also noticed this behavior—it happens on the iOS web version, but sometimes on the iOS native app as well.

After logging into the account and performing a clean installation of the app, when the user opens a transaction for the first time, thumbnail320 is initially displayed, after which it is replaced by the full image; however, this replacement does not occur smoothly, as it does on the web on a PC, for example—instead, the image disappears and then reappears.

Can you recheck this on main?

This is how it behaves on my main. It looks like your description so this is probably a separate issue

Nagranie.z.ekranu.2026-05-5.o.12.11.24.mov

[Eskalifer1]

Yeah, I know it's in the main branch, but it seems like the changes in this PR have made it more noticeable. If you think it's okay, then we can leave it as is.

[sosek108]

I'll try to handle this, but the issue is somewhere else.
On the attached video you can see that MoneyRequestReceiptView component is mounted and unmounted multiple times when opening a report.

Nagranie.z.ekranu.2026-05-5.o.12.57.35.mov

[sosek108]

After some investigation I'm not able to easily fix this.

The thumbnail feature itself is correct — the glitches are entirely from pre-existing remounting instability that causes ImageWithLoading to restart from scratch each time. I'd propose to create new issue for this and handle this separately

CC: @marcaaron

[sosek108]

Yeah, I think it’s my fault—turning on Use Staging Server actually made it work as it should.

I noticed this; it looks like a bug. To reproduce it, you need to:

• Log in to your account, of course in incognito mode and with the cache cleared.
• Go to the Spend page
• Use F12 to simulate offline mode (It’s important to use F12 specifically, since in-app offline mode doesn’t block image loading)
• Go to the expense with the receipt
• A thumbnail with a lower resolution is displayed (as expected), but when you try to open it, it gets stuck loading indefinitely. There is no thumbnail on the stage, and when you try to open it, a loader appears, but after that, an offline page appears.

2026-04-30.23.19.54.mov
What do you think about this?

I can reproduce this on main so this again looks like something different.

Nagranie.z.ekranu.2026-05-5.o.13.48.55.mov

[sosek108]

Please also add videos for iOS Web and Android Web

done.

[Eskalifer1]

Well, of course, I didn’t insist on fixing it, since I already know these behavior are in the main branch.

I was just curious to hear your thoughts on this, because sometimes certain changes can make bugs (or certain behaviors) that were already there more noticeable. If QA asks about this, we’ll be able to tell them that it’s already in the main branch.

[Eskalifer1]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

android-native.mov

Android: mWeb Chrome

android-web.mov

iOS: HybridApp

ios-native.mov

iOS: mWeb Safari

ios-web.mov

MacOS: Chrome / Safari

web.mov

[Eskalifer1]

One last question I have: what do you think about adding a note to the Tests section explaining that this preview appears frequently, but not always, depending on various factors, for example, this is clearly visible in the videos you recorded, especially on Android native, where the low-resolution preview doesn’t always have time to load when opening; I’ve also encountered this, especially on native platforms

[sosek108]

@marcaaron (cc: @mountiny)

There are two issues that are on main:

1. Show thumbnail preview while receipt image loads #88575 (review)
2. Show thumbnail preview while receipt image loads #88575 (review)

From UX perspective they look like related to my changes but deep dive to codebase and the root cause is in other places. I think we should work on these but propose to do them in separate issues. What do you think?

[sosek108]

One last question I have: what do you think about adding a note to the Tests section explaining that this preview appears frequently, but not always, depending on various factors, for example, this is clearly visible in the videos you recorded, especially on Android native, where the low-resolution preview doesn’t always have time to load when opening; I’ve also encountered this, especially on native platforms

Right, we should describe these

[Eskalifer1]

@marcaaron (cc: @mountiny)

There are two issues that are on main:

1. Show thumbnail preview while receipt image loads #88575 (review)
2. Show thumbnail preview while receipt image loads #88575 (review)

From UX perspective they look like related to my changes but deep dive to codebase and the root cause is in other places. I think we should work on these but propose to do them in separate issues. What do you think?

I agree, let's see what others say

[Eskalifer1]

LGTM!

[Eskalifer1]

Should we put this on hold?

cc: @marcaaron @sosek108

[marcaaron]

Yes. Who is looking into the fix PR? Do we need another issue for that or handling it here?

[sosek108]

@marcaaron I think I can look into it, but currently I'm helping with Onyx investigation which is a little bit more urgent for me. I should be able to get back here this week

[sosek108]

@Eskalifer1

can you retest this one? #88575 (review)

[Eskalifer1]

Hi @sosek108, Yep, it works much more smoothly now!

Let's remove “HOLD” from the name and fix the ESLint rules

[Eskalifer1]

Hi @Expensify/design, while working on this PR, I noticed a small UI inconsistency related to the trip details section. Specifically, the indentation between “Passenger” and the following element differs depending on whether we are on “Rail details” or “Train details.”

The fix itself is very straightforward (just a one-line change). If we decide it’s worth addressing, I’d be happy to help with it — either by working on it together with Melvin as C+, or by opening a small PR myself if that’s preferred.

2026-05-20.17.08.30.mov

[shawnborton]

Yeah I think we should fix it 👍 working with Melvin seems like a good idea.

[Eskalifer1]

@shawnborton Can you please create an issue for that and assign me pls ^)

[sosek108]

@Eskalifer1 all checks are passing now!

[sosek108]

@marcaaron Can we proceed with merging this?