[Odometer] Image stitching

[jakubkalinski0]

Explanation of Change

This PR implements the next part of the Odometer feature. It adds the image stitching/merging flow that automatically combines the start and end odometer photos into a single receipt image.

• Image stitching library (src/libs/stitchOdometerImages/):

  • stitchLayout.ts - Calculates optimal layout: if both images are portrait (height > width), arrange vertically, if there is at least one landscape then we arrange them horizontally.
  • index.ts (web) - Uses the HTML Canvas API to draw both images onto an offscreen canvas, exports as a blob URL. Revokes the previous blob URL to prevent memory leaks (only one URL is kept at a time).
  • index.native.ts (native) - Uses @shopify/react-native-skia for GPU-accelerated compositing. Fetches images as ArrayBuffers, renders to an offscreen Skia surface, encodes to base64, and writes to a temporary file. Deletes any previously stitched file before creating a new one to avoid accumulating temp files.

• IOURequestStepDistanceOdometer.tsx integration:

  • When we have 2 images stitchOdometerImages(startImage, endImage) is called inside navigateToNextPage
  • The stitched image is set as the transaction receipt via setMoneyRequestReceipt
  • When there is only one odometer image, we set it as a receipt

Fixed Issues

$ #77267
PROPOSAL: N/A

Tests

Both images scenario:

1. Press FAB -> go to "Track distance" -> choose "Odometer" tab
2. Enter start and end odometer readings
3. Press on the photo thumbnail -> capture or pick an image -> verify it is shown in the thumbnail (do that for both Start and End)
4. Press "Next" -> verify no error is shon and navigation proceeds normally
5. On the confirmation screen verify that the receipt shown is a single stitched image containing both odometer photos (arranged 1 above the other if there was at least 1 landscape image, or stacked vertically for 2 portrait images - example on image below)

6. Go to distance, replace the start or end photo -> press "Save" -> verify the new stitched image now uses the updated start/end photo

Single image scenario:

7. Repeat steps 1-2, but capture only the start or end photo (leave the other photo thumbnail empty) -> press "Next" -> verify navigation proceeds without errors and the single photo alone is used as the receipt

Delete one image after adding both:

8. Repeat steps 1-4 to capture both photos -> on the confirmation screen go to distance -> press on the Start or End photo thumbnail -> press "Three dots menu" -> press "Delete" -> verify the thumbnail returns to the empty state -> press "Next" -> verify the end photo alone is used as the receipt

• Verify that no errors appear in the JS console

Offline tests

Same as Tests

QA Steps

Same as Tests

• Verify that no errors appear in the JS console

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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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: https://swmansion.slack.com/archives/C01GTK53T8Q/p1773238989928089
  • 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

iOS needs to be tested on a physcical device

Android: Native

1to6.webm

7.webm

8.webm

Android: mWeb Chrome

1to6mweb.webm

7mweb.webm

8mweb.webm

MacOS: Chrome / Safari

1to6.mov

7.mov

8.mov

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
.../components/MoneyRequestConfirmationListFooter.tsx	83.89% <100.00%> (+0.04%)	⬆️
...request/step/IOURequestStepOdometerImage/index.tsx	0.00% <0.00%> (ø)
src/libs/actions/IOU/index.ts	72.86% <0.00%> (ø)
...alScreen/routes/TransactionReceiptModalContent.tsx	0.00% <0.00%> (ø)
...ou/request/step/IOURequestStepDistanceOdometer.tsx	0.00% <0.00%> (ø)
src/libs/stitchOdometerImages/stitchLayout.ts	0.00% <0.00%> (ø)
src/libs/stitchOdometerImages/index.ts	0.00% <0.00%> (ø)
src/libs/stitchOdometerImages/index.native.ts	0.00% <0.00%> (ø)
... and 47 files with indirect coverage changes

[Julesssss]

Hey @jakubkalinski0, the linked PR was merged, is this ready for review?

[jakubkalinski0]

Hey @jakubkalinski0, the linked PR was merged, is this ready for review?

Yes it is. I will just test it and add videos to the PR description and we are good to go with the review

[melvin-bot]

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

[DylanDylann]

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
  • MacOS: Desktop
• 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 there are no new alerts related to the canBeMissing param for useOnyx
• 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

Screen.Recording.2026-03-13.at.18.42.51.mov

Android: mWeb Chrome

Screen.Recording.2026-03-13.at.18.37.49.mov

iOS: HybridApp

Screen.Recording.2026-03-13.at.18.41.06.mov

iOS: mWeb Safari

Screen.Recording.2026-03-13.at.18.38.42.mov

MacOS: Chrome / Safari

Screen.Recording.2026-03-13.at.18.30.00.mov

[DylanDylann]

@Expensify/design Could you take a look at the stitching image below? Do you think we should display it smaller so users can see it fully? Currently, the preview is cut off, and users can only see the full image by clicking on it.

Screen.Recording.2026-03-13.at.18.30.00.mov

Another case on mobile where the second image is only partially displayed.

Screen.Recording.2026-03-13.at.18.38.42.mov

[DylanDylann]

@jakubkalinski0 The rest looks fine to me

[jakubkalinski0]

@DylanDylann Then I guess we wait for the designs decision. In the meantime I will implement the adjusted preview and have it ready on hand.

[jakubkalinski0]

If we are already in the topic of clarifying where do we want the preview adjusted then I would like to list all the places that could potentially look problematic. I think those are all places (if I missed any please correct me). Which ones would we like to adjust? Some/all/none of them?

[jakubkalinski0]

@DylanDylann I've caught one small issue/bug, so I fixed it already. It's a very small change

[jakubkalinski0]

@Julesssss Maybe we should move that discussion to the followup and get this PR going?

[Julesssss]

@Julesssss Maybe we should move that discussion to the followup and get this PR going?

Yeah, exactly what I was thinking this morning. Unfortunately the failing test case does appear to be failng with the latest changes.

Actually perhaps it's coincidentally related... Will rerun again 🤞

[Julesssss]

Approving the final commit

[Julesssss]

Tests passing. We'll merge this final feature and can discuss the image stitching alignment separately.

[jakubkalinski0]

Actually perhaps it's coincidentally related... Will rerun again

Yeah I think it is. This test job has been acting up this week

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

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

[github-actions]

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-679e152-2ebebc3-4e2936ca25e694ccc24a61569fd90136e96a6d56/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-679e152-2ebebc3-bd254ac439d9fbcd7b1118ccc3e02909f3818951/index.html

Web 🕸️
https://83556.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.3.38-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[nlemma]

Deploy Blocker #85368 was identified to be related to this PR.

[mitarachim]

Deploy Blocker #85365 was identified to be related to this PR.

[mitarachim]

Deploy Blocker #85405 was identified to be related to this PR.

[Julesssss]

Added the three issues to the main tracker as bugs.

[OSBotify]

🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.38-4 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅