Skip to content

Update Thumbnails in expense details and report preview#87056

Closed
sosek108 wants to merge 2 commits intoExpensify:mainfrom
callstack-internal:fix/thumbnails
Closed

Update Thumbnails in expense details and report preview#87056
sosek108 wants to merge 2 commits intoExpensify:mainfrom
callstack-internal:fix/thumbnails

Conversation

@sosek108
Copy link
Copy Markdown
Contributor

@sosek108 sosek108 commented Apr 3, 2026

Explanation of Change

The PR #86512 introduced a localSource field on transaction.receipt to preserve the local file URI when a scan expense is created, preventing the server's remote URL from causing an unnecessary image reload. ReportActionItemImage renders localSource ?? source, so the locally available image is shown immediately without re-downloading. The regression fix adds localSource: null to receiptOptimistic in replaceReceipt, ensuring that when a receipt is rotated or cropped the stale local URI is cleared and the freshly updated image is displayed correctly.

Fixed Issues

$ #87051
PROPOSAL:

Tests

  1. Open the Expensify app
  2. Go to the workspace chat
  3. Create a report and add a scan expense
  4. Add a manual expense
  5. Go to the scan expense details
  6. Tap on the receipt preview
  7. Tap on Rotate or Crop and save the changes
  8. Tap the left arrow in the top-left corner, verifying every screen where the receipt thumbnail appears

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  1. Open the Expensify app
  2. Go to the workspace chat
  3. Create a report and add a scan expense
  4. Add a manual expense
  5. Go to the scan expense details
  6. Tap on the receipt preview
  7. Tap on Rotate or Crop and save the changes
  8. Tap the left arrow in the top-left corner, verifying every screen where the receipt thumbnail appears

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: mWeb Chrome
iOS: Native
Nagranie.z.ekranu.2026-04-3.o.09.45.04.mov
iOS: mWeb Safari
MacOS: Chrome / Safari

@sosek108 sosek108 marked this pull request as ready for review April 3, 2026 08:57
@sosek108 sosek108 requested review from a team as code owners April 3, 2026 08:57
@melvin-bot melvin-bot bot requested a review from ikevin127 April 3, 2026 08:57
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 3, 2026

@ikevin127 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]

@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and removed request for a team April 3, 2026 08:57
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d0020220fd

ℹ️ 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".

const oldReceipt = transaction?.receipt ?? {};
const receiptOptimistic = {
source,
localSource: null,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve new local URI when replacing a receipt

Setting receiptOptimistic.localSource to null causes ReportActionItemImage to treat localSource as defined (localSource !== undefined) and overwrite a string image with null, which yields an empty resolved image source during optimistic updates. In the rotate/crop replaceReceipt flow this can make the receipt preview disappear (notably in wide RHP where shouldUseThumbnailImage is false) until the server response arrives, and it remains user-visible on slow/offline connections.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sosek108 did you see this? Any thoughts here?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed — this is a real issue. Here's the trace:

replaceReceipt sets localSource: null in receiptOptimistic (correct Onyx semantics — you need explicit null to clear a key on merge). But ReportActionItemImage.tsx line 140 uses a strict !== undefined guard:

const effectiveImage = localSource !== undefined && typeof image === 'string' ? localSource : image;

When localSource = null:

  • null !== undefinedtrue ← the problem
  • condition passes → effectiveImage = null
  • Line 142: tryResolveUrlFromApiRoot(null ?? '') → resolves to an empty string

So during the optimistic update after rotate/crop, the receipt image goes blank until the server responds. On slow or offline connections this is user-visible.

Line 139 is fine — null ?? thumbnail correctly falls back via nullish coalescing. Only line 140 needs fixing.

Fix needed in ReportActionItemImage.tsx line 140:

// before
const effectiveImage = localSource !== undefined && typeof image === 'string' ? localSource : image;
// after
const effectiveImage = localSource != null && typeof image === 'string' ? localSource : image;

!= null (loose equality) catches both null and undefined as "no local source", which is the correct semantic. The localSource: null in the optimistic data is right — it just needs a corresponding update to the consumer.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 3, 2026

🚧 @Beamanator has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 3, 2026

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #87056.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Android was skipped The build for iOS was skipped
Web 🕸️
https://87056.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@situchan
Copy link
Copy Markdown
Contributor

situchan commented Apr 3, 2026

Please also fix #87029 (another blocker) as well

@Beamanator
Copy link
Copy Markdown
Contributor

Looks like Melvin is suggesting basically the same change to fix that blocker too - see here: #87029 (comment)

@sosek108
Copy link
Copy Markdown
Contributor Author

sosek108 commented Apr 3, 2026

Closing in favor of #87091

@sosek108 sosek108 closed this Apr 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants