Skip to content

[Odometer] Image capture for native#82432

Merged
Julesssss merged 28 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_Add_image_capture_for_native
Feb 24, 2026
Merged

[Odometer] Image capture for native#82432
Julesssss merged 28 commits intoExpensify:mainfrom
software-mansion-labs:jakubkalinski0/Odometer_Add_image_capture_for_native

Conversation

@jakubkalinski0
Copy link
Contributor

@jakubkalinski0 jakubkalinski0 commented Feb 13, 2026

Explanation of Change

This PR implements the next part of the Odometer feature, aligned with Phase 1 task 1.D. This PR focuses on the native implementation of the image capture flow with mobile web implementation to follow

  • 1.D (Capture start/end images) - added a complete implementation of src/pages/iou/request/step/IOURequestStepOdometerImage/index.native.tsx. We intentionally did not reuse IOURequestStepScan because that screen includes receipt‑specific behaviors (SmartScan, receipt state logic). The implementation covers all the following aspects:
    • Camera permissions logic,
    • Flash logic,
    • Photo/file picker,
    • Taking the photo and saving it.

Due to duplicated logic across IOURequestStepOdometerImage and IOURequestStepScan there is a plan to introduce more abstraction for the camera related logic/features in a followup once the Odometer project is done.

Fixed Issues

$ #77266
PROPOSAL: N/A

Tests

Important

  • Only native - mWeb isn't implemented yet
  • iOS simulator doesn't support camera functionality so if you want to test it you have to use a physical device
  • If you want to test functionality of flash you also need to use a physical device as you cannot actually observe if it works
image

Caution

Use Android emulator or a physical device for testing - explanation above ^

Prerequisites:
Turn off camera permissions for Expensify -> the most convenient for you would probably be to set "Ask every time"

  1. Press FAB -> go to "Track distance" -> choose "Odometer" tab`
  2. Press on the Thumbnail -> you should see the screen shown below
permission
  1. Press "Continue" -> verify that you are shown a native prompt asking you to allow Expensify to use the camera
permission request
  1. Press "Only this time" (pressing "While using this app" would behave the same but will require you to turn off camera permissions for Expensify once again later) -> verify that you now have access to the camera (the screen from step 2 is gone and you see a working camera display like the one below)
working camera emulated-flash

Important

If your device has no back camera then you will see an infinite loader (same behavior as in the scan component)
loader

Important

If your device has no flash then the Bolt icon of flash in the top right corner will be hidden - in order to test the flash itself you have to do it on a physical device no matter if your simulator "has" a flash
Screenshot 2026-02-20 at 17 49 22

  1. Take the photo -> verify that the camera is closed and you are brought back to the Odometer page with the photo you have just taken being displayed correctly in the thumbnail
working thumbnail
  1. Verify that when you press on the thumbnail once again then you are brought to the Image Preview and it displays the photo correctly
  2. Then press on the Three dots menu and verify that when you press "Replace" then you are brought to the Camera photo capture and that it works correctly
  3. Now rebuild the app in order to reset the permissions (or turn them off once again if you chose "While using this app" earlier)
  4. Repeat the steps 1 through 3 but now press "Don't allow" when asked about camera permissions -> verify that you are still at this screen
camera permissions2
  1. Now press "Continue" once again and verify that you are shown this prompt below
App screenshot 2026-02-20 17 08 32

Important

You will probably be shown this prompt more than once when pressing "Continue" before you are shown the prompt redirecting you to "Settings". If that happens then simply press "Don't allow" until you see a prompt from step 11
promptbasic

  1. When you press "Cancel" the prompt should be simply closed but when you press "Settings" verify that you are brought to the device settings
Settings
  1. Change the camera permissions for Expensify (either to "While using this app" or "Ask every time") and verify that when you go back to the Expensify you are brought:
    • directly to the Camera photo capture if you chose "While using this app"
    • or to the "Take a photo" if you chose "Ask every time" -> then you will have to press continue and you will be prompted once again by the original prompt to "Allow Expensify...".

When you are finally on the Camera photo capture verify that it works properly.

  1. Now Press the Gallery icon at the bottom left corner and verify that all the 3 options work properly
gallery take gallery2 files
  1. (optional, but recommended) Now repeat the steps 1 through 13 for End odometer photo (although if everything worked properly for Start photo then it will work the same for the End photo)
    • (Noticeable difference) The information box at the bottom of the camera field should display information (i.e. icon/text) about the End odometer photo

Warning

When testing End odometer photo after the Start odometer phot" your camera permissions for Expensify were probably set to "Don't allow" after the step 9 so you will have to change it to "Ask every time" when testing the second photo flow

  • 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

Android: Native

Steps 1 through 7:

1to7.mp4

Steps 8 through 12:

8to12.mp4

Step 13:

13.mp4
iOS: Native

iOS simulator does not support camera so you can actually observe the correct behavior for this situation (lack of back camera) mentioned in the step 4 Important section 1 - i.e. an infinite loader:

ios.mp4

@codecov
Copy link

codecov bot commented Feb 13, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 92.43% <ø> (ø)
src/styles/index.ts 46.87% <ø> (+0.52%) ⬆️
src/styles/variables.ts 100.00% <ø> (ø)
.../step/IOURequestStepOdometerImage/index.native.tsx 0.00% <0.00%> (ø)
... and 45 files with indirect coverage changes

@jakubkalinski0 jakubkalinski0 force-pushed the jakubkalinski0/Odometer_Add_image_capture_for_native branch from 603fe12 to b58813d Compare February 19, 2026 12:21
@melvin-bot
Copy link

melvin-bot bot commented Feb 19, 2026

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

@github-actions
Copy link
Contributor

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

@github-actions

This comment has been minimized.

@jakubkalinski0
Copy link
Contributor Author

jakubkalinski0 commented Feb 20, 2026

Failing TypeScript check is caused only by the lack of translations - besides that all is well ✅

@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 9c495ed5..25e4c4c2 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7551,6 +7551,9 @@ Fordern Sie Spesendetails wie Belege und Beschreibungen an, legen Sie Limits und
             endTitle: 'Kilometerzähler-Endfoto',
             deleteOdometerPhoto: 'Kilometerzähler-Foto löschen',
             deleteOdometerPhotoConfirmation: 'Möchtest du dieses Kilometerzählerfoto wirklich löschen?',
+            cameraAccessRequired: 'Für das Aufnehmen von Bildern ist der Kamerazugriff erforderlich.',
+            snapPhotoStart: '<muted-text-label>Machen Sie zu <strong>Beginn</strong> Ihrer Fahrt ein Foto von Ihrem Kilometerzähler.</muted-text-label>',
+            snapPhotoEnd: '<muted-text-label>Machen Sie ein Foto von Ihrem Kilometerzähler am <strong>Ende</strong> Ihrer Fahrt.</muted-text-label>',
         },
     },
     gps: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 1f1c9f1f..b17c07e0 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7573,6 +7573,9 @@ Rendez obligatoires des informations de dépense comme les reçus et les descrip
             endTitle: 'Photo du compteur (arrivée)',
             deleteOdometerPhoto: 'Supprimer la photo du compteur kilométrique',
             deleteOdometerPhotoConfirmation: 'Voulez-vous vraiment supprimer cette photo de l’odomètre ?',
+            cameraAccessRequired: "L'accès à l'appareil photo est requis pour prendre des photos.",
+            snapPhotoStart: '<muted-text-label>Prenez une photo de votre compteur kilométrique au <strong>début</strong> de votre trajet.</muted-text-label>',
+            snapPhotoEnd: '<muted-text-label>Prenez une photo de votre compteur kilométrique à la <strong>fin</strong> de votre trajet.</muted-text-label>',
         },
     },
     gps: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 20f9ef14..00d02351 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7537,6 +7537,9 @@ Richiedi dettagli sulle spese come ricevute e descrizioni, imposta limiti e valo
             endTitle: 'Foto contachilometri finale',
             deleteOdometerPhoto: 'Elimina foto del contachilometri',
             deleteOdometerPhotoConfirmation: 'Sei sicuro di voler eliminare questa foto del contachilometri?',
+            cameraAccessRequired: 'Per scattare foto è necessario l’accesso alla fotocamera.',
+            snapPhotoStart: "<muted-text-label>Scatta una foto del contachilometri all'<strong>inizio</strong> del viaggio.</muted-text-label>",
+            snapPhotoEnd: '<muted-text-label>Scatta una foto del contachilometri alla <strong>fine</strong> del viaggio.</muted-text-label>',
         },
     },
     gps: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index e4aaa48a..0233d855 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7462,6 +7462,9 @@ ${reportName}
             endTitle: '走行距離計(終了時)の写真',
             deleteOdometerPhoto: '走行距離計の写真を削除',
             deleteOdometerPhotoConfirmation: 'この走行距離計の写真を削除してもよろしいですか?',
+            cameraAccessRequired: '写真を撮影するにはカメラへのアクセス権限が必要です。',
+            snapPhotoStart: '<muted-text-label>移動を<strong>開始</strong>するときに、走行距離計の写真を撮影してください。</muted-text-label>',
+            snapPhotoEnd: '<muted-text-label>走行の<strong>終了時</strong>に、オドメーターの写真を撮影してください。</muted-text-label>',
         },
     },
     gps: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 140fb8b0..59900a88 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7516,6 +7516,9 @@ Vereis onkostendetails zoals bonnen en beschrijvingen, stel limieten en standaar
             endTitle: 'Eindfoto kilometerteller',
             deleteOdometerPhoto: 'Kilometerstandfoto verwijderen',
             deleteOdometerPhotoConfirmation: 'Weet je zeker dat je deze kilometertellerfoto wilt verwijderen?',
+            cameraAccessRequired: 'Cameratoegang is nodig om foto’s te maken.',
+            snapPhotoStart: '<muted-text-label>Maak een foto van je kilometerteller aan het <strong>begin</strong> van je rit.</muted-text-label>',
+            snapPhotoEnd: '<muted-text-label>Maak een foto van je kilometerteller aan het <strong>einde</strong> van je rit.</muted-text-label>',
         },
     },
     gps: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index e0dbafea..43da6c83 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7503,6 +7503,9 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
             endTitle: 'Końcowe zdjęcie licznika przebiegu',
             deleteOdometerPhoto: 'Usuń zdjęcie licznika przebiegu',
             deleteOdometerPhotoConfirmation: 'Na pewno chcesz usunąć to zdjęcie licznika?',
+            cameraAccessRequired: 'Aby robić zdjęcia, wymagany jest dostęp do aparatu.',
+            snapPhotoStart: '<muted-text-label>Zrób zdjęcie licznika kilometrów na <strong>początku</strong> podróży.</muted-text-label>',
+            snapPhotoEnd: '<muted-text-label>Zrób zdjęcie licznika kilometrów na <strong>koniec</strong> swojej podróży.</muted-text-label>',
         },
     },
     gps: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 4026f03c..4bd4d888 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7508,6 +7508,9 @@ Exija dados de despesas como recibos e descrições, defina limites e padrões e
             endTitle: 'Foto final do hodômetro',
             deleteOdometerPhoto: 'Excluir foto do odômetro',
             deleteOdometerPhotoConfirmation: 'Tem certeza de que deseja excluir esta foto do odômetro?',
+            cameraAccessRequired: 'É necessário acessar a câmera para tirar fotos.',
+            snapPhotoStart: '<muted-text-label>Tire uma foto do odômetro no <strong>início</strong> da sua viagem.</muted-text-label>',
+            snapPhotoEnd: '<muted-text-label>Tire uma foto do odômetro no <strong>final</strong> da sua viagem.</muted-text-label>',
         },
     },
     gps: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 98e3dea5..cd91887d 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -7344,6 +7344,9 @@ ${reportName}
             endTitle: '结束里程表照片',
             deleteOdometerPhoto: '删除里程表照片',
             deleteOdometerPhotoConfirmation: '确定要删除这个里程表照片吗?',
+            cameraAccessRequired: '拍照需要启用相机访问权限。',
+            snapPhotoStart: '<muted-text-label>在行程<strong>开始</strong>时拍一张里程表照片。</muted-text-label>',
+            snapPhotoEnd: '<muted-text-label>在行程<strong>结束</strong>时拍一张里程表的照片。</muted-text-label>',
         },
     },
     gps: {

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 jakubkalinski0 marked this pull request as ready for review February 20, 2026 19:24
@jakubkalinski0 jakubkalinski0 requested review from a team as code owners February 20, 2026 19:24
@jakubkalinski0
Copy link
Contributor Author

prettier check failing - in unrelated files that weren't changed in this PR

@DylanDylann
Copy link
Contributor

The code changes look fine. I'll complete my testing soon (early tomorrow)

Copy link
Contributor

@joekaufmanexpensify joekaufmanexpensify left a comment

Choose a reason for hiding this comment

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

Whats next project

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

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

Android 🤖 iOS 🍎
❌ FAILED ❌ https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-c7c8dc9-3a2d3ff-5e0fa83d1c8d202155b746f73a991d98b7f1ee6e/index.html
The QR code can't be generated, because the Android build failed iOS
Web 🕸️
https://82432.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@DylanDylann
Copy link
Contributor

@jakubkalinski0 Please merge new main

@DylanDylann
Copy link
Contributor

DylanDylann commented Feb 24, 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-02-24.at.12.52.17.mov
iOS: HybridApp
Screen.Recording.2026-02-24.at.12.42.02.mov

@DylanDylann
Copy link
Contributor

@jakubkalinski0 NAB: but good to update: #82432 (comment)

@melvin-bot melvin-bot bot requested a review from Julesssss February 24, 2026 11:34
@jakubkalinski0
Copy link
Contributor Author

jakubkalinski0 commented Feb 24, 2026

@DylanDylann I am aware this comment is pretty valid but wasn't sure what to do with all the other magic numbers with the same values that I used. I will add those values used by me to variables now but I will leave all otherr untouched

@Julesssss
Copy link
Contributor

Thanks for the detailed review. I created this follow up improvement issue to help us move forward and added it to the tracker.

@Julesssss Julesssss merged commit 5e00a65 into Expensify:main Feb 24, 2026
32 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.

@OSBotify
Copy link
Contributor

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

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

@mitarachim
Copy link

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.3.26-8 🚀

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

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.

6 participants