Skip to content

[Odometer] Image stitching#83556

Merged
Julesssss merged 28 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_Add_merged_image_flow
Mar 13, 2026
Merged

[Odometer] Image stitching#83556
Julesssss merged 28 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_Add_merged_image_flow

Conversation

@jakubkalinski0
Copy link
Contributor

@jakubkalinski0 jakubkalinski0 commented Feb 26, 2026

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)
image
  1. 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:

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

  1. 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
    • 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
Copy link

codecov bot commented Mar 3, 2026

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
Copy link
Contributor

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

@jakubkalinski0
Copy link
Contributor Author

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

@jakubkalinski0 jakubkalinski0 marked this pull request as ready for review March 10, 2026 12:53
@jakubkalinski0 jakubkalinski0 requested review from a team as code owners March 10, 2026 12:53
@melvin-bot melvin-bot bot requested review from mjasikowski and trjExpensify and removed request for a team March 10, 2026 12:53
@melvin-bot
Copy link

melvin-bot bot commented Mar 10, 2026

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

@OSBotify
Copy link
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index cf894701..fffbe2c3 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1445,6 +1445,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: 'Das Enddatum darf nicht mit dem Startdatum übereinstimmen',
             manySplitsProvided: `Die maximale Anzahl zulässiger Aufteilungen beträgt ${CONST.IOU.SPLITS_LIMIT}.`,
             dateRangeExceedsMaxDays: `Der Datumsbereich darf ${CONST.IOU.SPLITS_LIMIT} Tage nicht überschreiten.`,
+            stitchOdometerImagesFailed: 'Kilometerzählerbilder konnten nicht zusammengeführt werden. Bitte versuchen Sie es später noch einmal.',
         },
         dismissReceiptError: 'Fehler ausblenden',
         dismissReceiptErrorConfirmation: 'Achtung! Wenn du diesen Fehler schließt, wird deine hochgeladene Quittung vollständig entfernt. Bist du sicher?',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 90d1bc29..c01c3ada 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1449,6 +1449,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: 'La date de fin ne peut pas être identique à la date de début',
             manySplitsProvided: `Le nombre maximal de répartitions autorisées est de ${CONST.IOU.SPLITS_LIMIT}.`,
             dateRangeExceedsMaxDays: `La plage de dates ne peut pas dépasser ${CONST.IOU.SPLITS_LIMIT} jours.`,
+            stitchOdometerImagesFailed: 'Échec de la combinaison des images de l’odomètre. Veuillez réessayer plus tard.',
         },
         dismissReceiptError: 'Ignorer l’erreur',
         dismissReceiptErrorConfirmation: 'Attention ! Ignorer cette erreur supprimera complètement votre reçu téléversé. Êtes-vous sûr ?',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index f8387f93..89db03bc 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1442,6 +1442,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: 'La data di fine non può essere uguale alla data di inizio',
             manySplitsProvided: `Il numero massimo di suddivisioni consentite è ${CONST.IOU.SPLITS_LIMIT}.`,
             dateRangeExceedsMaxDays: `L’intervallo di date non può superare ${CONST.IOU.SPLITS_LIMIT} giorni.`,
+            stitchOdometerImagesFailed: 'Impossibile combinare le immagini del contachilometri. Riprova più tardi.',
         },
         dismissReceiptError: 'Ignora errore',
         dismissReceiptErrorConfirmation: 'Attenzione! Chiudere questo errore rimuoverà completamente la ricevuta che hai caricato. Sei sicuro?',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index b0d71e2c..a47570b1 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1433,6 +1433,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: '終了日は開始日と同じにはできません',
             manySplitsProvided: `分割できる最大数は${CONST.IOU.SPLITS_LIMIT}件です。`,
             dateRangeExceedsMaxDays: `日付範囲は${CONST.IOU.SPLITS_LIMIT}日を超えることはできません。`,
+            stitchOdometerImagesFailed: '走行距離計の画像を結合できませんでした。後でもう一度お試しください。',
         },
         dismissReceiptError: 'エラーを閉じる',
         dismissReceiptErrorConfirmation: 'ご注意ください!このエラーを閉じると、アップロード済みのレシートが完全に削除されます。本当に続行しますか?',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 19e934b4..70d71a39 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1440,6 +1440,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: 'De einddatum mag niet gelijk zijn aan de startdatum',
             manySplitsProvided: `Het maximale aantal toegestane splitsingen is ${CONST.IOU.SPLITS_LIMIT}.`,
             dateRangeExceedsMaxDays: `Het datumbereik mag niet meer dan ${CONST.IOU.SPLITS_LIMIT} dagen zijn.`,
+            stitchOdometerImagesFailed: 'Odometerafbeeldingen combineren mislukt. Probeer het later opnieuw.',
         },
         dismissReceiptError: 'Foutmelding sluiten',
         dismissReceiptErrorConfirmation: 'Let op! Dit foutbericht negeren verwijdert je geüploade bon volledig. Weet je het zeker?',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 280523cb..be773c96 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1439,6 +1439,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: 'Data zakończenia nie może być taka sama jak data rozpoczęcia',
             manySplitsProvided: `Maksymalna dozwolona liczba podziałów to ${CONST.IOU.SPLITS_LIMIT}.`,
             dateRangeExceedsMaxDays: `Zakres dat nie może przekraczać ${CONST.IOU.SPLITS_LIMIT} dni.`,
+            stitchOdometerImagesFailed: 'Nie udało się połączyć zdjęć licznika kilometrów. Spróbuj ponownie później.',
         },
         dismissReceiptError: 'Odrzuć błąd',
         dismissReceiptErrorConfirmation: 'Uwaga! Zamknięcie tego błędu spowoduje całkowite usunięcie przesłanego paragonu. Czy na pewno chcesz kontynuować?',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ccc0a57f..55ea73c1 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1437,6 +1437,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: 'A data de término não pode ser igual à data de início',
             manySplitsProvided: `O número máximo de divisões permitido é ${CONST.IOU.SPLITS_LIMIT}.`,
             dateRangeExceedsMaxDays: `O intervalo de datas não pode exceder ${CONST.IOU.SPLITS_LIMIT} dias.`,
+            stitchOdometerImagesFailed: 'Falha ao combinar imagens do hodômetro. Tente novamente mais tarde.',
         },
         dismissReceiptError: 'Dispensar erro',
         dismissReceiptErrorConfirmation: 'Atenção! Ignorar este erro removerá completamente o comprovante que você enviou. Tem certeza?',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 8a754ecc..192f3125 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1410,6 +1410,7 @@ const translations: TranslationDeepObject<typeof en> = {
             endDateSameAsStartDate: '结束日期不能与开始日期相同',
             manySplitsProvided: `允许的最大拆分数为 ${CONST.IOU.SPLITS_LIMIT}。`,
             dateRangeExceedsMaxDays: `日期范围不能超过 ${CONST.IOU.SPLITS_LIMIT} 天。`,
+            stitchOdometerImagesFailed: '合并里程表图片失败。请稍后重试。',
         },
         dismissReceiptError: '忽略错误',
         dismissReceiptErrorConfirmation: '提醒:关闭此错误将彻底删除你上传的收据。确定要继续吗?',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@jakubkalinski0
Copy link
Contributor Author

@DylanDylann Could you redo your review or maybe you @Julesssss want to do that?

@DylanDylann
Copy link
Contributor

I will review again totally. Thanks for the update

@jakubkalinski0
Copy link
Contributor Author

@DylanDylann When it comes to this discussion I have already created a draft PR here so we will be able to go ahead with that when this image stitching PR gets merged to the corresponding branch (so probably tomorrow?).

@jakubkalinski0
Copy link
Contributor Author

Failing job test is, as far as I can see, completely unrelated

@Julesssss
Copy link
Contributor

Test passed on retry

Julesssss
Julesssss previously approved these changes Mar 12, 2026
@Julesssss
Copy link
Contributor

I will review again totally. Thanks for the update

We're down to hopefully a final review 🤞

@Julesssss Julesssss requested a review from DylanDylann March 12, 2026 23:07
@DylanDylann
Copy link
Contributor

DylanDylann commented Mar 13, 2026

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
Copy link
Contributor

DylanDylann commented Mar 13, 2026

@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
Copy link
Contributor

@jakubkalinski0 The rest looks fine to me

@jakubkalinski0
Copy link
Contributor Author

@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
Copy link
Contributor Author

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?

Screenshot 2026-03-13 at 13 52 30 Screenshot 2026-03-13 at 13 51 41 Screenshot 2026-03-13 at 13 50 15

@jakubkalinski0
Copy link
Contributor Author

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

@jakubkalinski0
Copy link
Contributor Author

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

@Julesssss
Copy link
Contributor

Julesssss commented Mar 13, 2026

@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 🤞

Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

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

Approving the final commit

@Julesssss
Copy link
Contributor

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

@jakubkalinski0
Copy link
Contributor Author

jakubkalinski0 commented Mar 13, 2026

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

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

@Julesssss Julesssss merged commit 679e152 into Expensify:main Mar 13, 2026
48 of 50 checks passed
@OSBotify
Copy link
Contributor

✋ 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
Copy link
Contributor

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

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.

7 participants