[Odometer] Move odometer image stitching to confirmation page

[jakubkalinski0]

Explanation of Change

Moves odometer image stitching from the odometer reading step to the confirmation page. Previously, stitching blocked navigation with a loading button. Now, stitching runs on the confirmation page while an ActivityIndicator replaces the receipt preview, and errors surface via FormHelpMessage. Also extracts the stitched filename prefix to a constants file and skips stitching when only one image is present.

Fixed Issues

$ #84998
PROPOSAL: N/A

Tests

Important

This PR only moves the stitching logic to the confirmation page and does't introduce the backup transaction during editing from confirmation page (this will be added here #86022). Because of that when user makes any changes to the images when editing from confirmation page this change will be reflected on confirmation page as receipt will be re-stitched (no matter if he pressed "Save" or < back button)

We are testing the odometer expense creation flow which you start by doing the following:
Press FAB -> go to "Track distance" -> choose "Odometer" tab

Test 1 - Loading indicator while stitching

1. Create a new odometer distance expense.
2. Capture a start odometer photo and an end odometer photo and add both readings.
3. Navigate to the confirmation page.
4. Verify a loading indicator appears in the receipt thumbnail area while stitching runs, then the stitched combined image appears.

---

Test 2 - Re-stitching Deleting one photo clears the stale receipt
5. Create an odometer expense with start + end photos and navigate to the confirmation page.
6. Press "Distance" and replace/delete/crop/rotate one of the photos.
7. Then press "Save" and return to the confirmation page.
8. Verify that the receipt is re-stitched accordingly to the changes photo is adjusted to the changes (not the previously stitched version).

---

Test 3 - Single odometer image (no stitching)
9. Create an odometer expense but add only a start photo (skip the end photo).
10. Navigate to the confirmation page.
11. Verify the single image is shown as the receipt directly, with no loading indicator and no stitching attempt.

• 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 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

iOS needs to be tested on a physcical device

Android: Native

android.mp4

Android: mWeb Chrome

androidweb.mp4

iOS: mWeb Safari

ios.mp4

MacOS: Chrome / Safari

web.mp4

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/libs/stitchOdometerImages/constants.ts	100.00% <100.00%> (ø)
src/libs/stitchOdometerImages/index.ts	0.00% <0.00%> (ø)
...ou/request/step/IOURequestStepDistanceOdometer.tsx	0.00% <0.00%> (ø)
src/libs/stitchOdometerImages/index.native.ts	0.00% <0.00%> (ø)
src/components/MoneyRequestConfirmationList.tsx	61.78% <25.00%> (-0.26%)	⬇️
.../components/MoneyRequestConfirmationListFooter.tsx	82.80% <75.00%> (+0.19%)	⬆️
...alScreen/routes/TransactionReceiptModalContent.tsx	0.00% <0.00%> (ø)
...es/iou/request/step/IOURequestStepConfirmation.tsx	55.61% <23.68%> (-2.29%)	⬇️
... and 23 files with indirect coverage changes

[Julesssss]

I think this PR also will resolve this bug.

[melvin-bot]

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

[jakubkalinski0]

@DylanDylann I fixed one bug that I found but we should be good besides that

[github-actions]

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

[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 #85105.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-ca6fc8f-de8080e-d459597d17e42a4dbf5b626b9ecda63889d8a01e/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-ca6fc8f-de8080e-bc0c13363be86ba0671c974c4bdebea94a6a3aaa/index.html

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

---

👀 View the workflow run that generated this build 👀

[JmillsExpensify]

LGTM

[Julesssss]

@jakubkalinski0 some conflicts now 😢

[jakubkalinski0]

@Julesssss Thanks for tagging me! I will get back to my PC and solve it in a minute. Hopefully we can get it merged today and get started on the next PR 🤞

[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 #85105.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-68e2260-2cd04ad-1382b0bf72193e54416bf222ba15cf8f611277f4/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-68e2260-2cd04ad-7ada591b2d8385436f5465ba1574f2514a30dadb/index.html

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

---

👀 View the workflow run that generated this build 👀

[Julesssss]

Great stuff. This is testing very well. Much better UX with the loading happening on the confirmation page.

[Julesssss]

[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 #85105.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-e89a862-2cd04ad-1382b0bf72193e54416bf222ba15cf8f611277f4/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-e89a862-2cd04ad-7ada591b2d8385436f5465ba1574f2514a30dadb/index.html

Web 🕸️
https://85105.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.44-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

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

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/grgia in version: 9.3.48-2 🚀

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