Skip to content

fix: use in-app VisionCamera for chat attachment photos#87681

Draft
MelvinBot wants to merge 5 commits intomainfrom
claude-inAppCameraForAttachments
Draft

fix: use in-app VisionCamera for chat attachment photos#87681
MelvinBot wants to merge 5 commits intomainfrom
claude-inAppCameraForAttachments

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

@MelvinBot MelvinBot commented Apr 10, 2026

Explanation of Change

Replaces the external system camera intent with an in-app VisionCamera modal when taking photos via the chat attachment picker ("Take photo") on both Android and iOS.

Why: On Android, launching the external camera activity backgrounds Expensify, allowing the OS to reclaim memory and crash the app (#84018). The previous fix (PR #86981) addressed this but was reverted due to multiple deploy blockers. This PR re-implements the feature while addressing all reported issues.

Key improvements over the reverted PR:

Deploy Blocker Fix
#87443 — Unable to tap-to-focus Added Gesture.Tap() handler with animated focus indicator (same pattern as IOURequestStepScan)
#87444 — Not scrollable in landscape (permissions denied) Permission-denied view wrapped in ScrollView with landscape-specific padding
#87447 — iOS viewfinder rotated 90° in landscape Modal uses supportedOrientations={['portrait', 'landscape']} and lets VisionCamera handle orientation natively
#87448 — iOS avatar edit page loads infinitely Clean promise resolution flow — onCapture callback returns photo data directly, modal closes before resolving
#87451 — Android camera overlaps camera hole/nav bar Full safe area inset padding (useSafeAreaInsets) on all four edges
#87456 — iOS camera doesn't appear after granting permission AppState listener refreshes permission status when app returns to foreground

Changes:

  • New AttachmentCamera component using react-native-vision-camera (same library used by receipt scan)
  • Modified AttachmentPicker/index.native.tsx to show in-app camera instead of launching external camera intent
  • New camera-flip.svg icon and CameraFlip icon registration
  • Added receipt.flipCamera translation key to all language files

Fixed Issues

$ #84018

Tests

  1. Open any chat
  2. Tap + → Add attachment → Take photo
  3. Verify the in-app camera opens in a full-screen modal
  4. Tap on the camera viewfinder to focus — verify a focus indicator circle appears and animates
  5. Tap the flash button (left) — verify flash toggles on/off
  6. Tap the camera flip button (right) — verify camera switches between front and back
  7. Tap the shutter button — verify photo is captured and attached to the chat
  8. Repeat step 2 but deny camera permission when prompted — verify the permission-denied screen shows with "Continue" button
  9. Rotate the device to landscape while on the permission-denied screen — verify the content is scrollable
  10. Grant camera permission from device Settings and return to the app — verify the camera viewfinder appears automatically
  11. Go to Account → Profile → Upload photo → Take photo — verify the photo is captured and the avatar edit page loads correctly (not infinitely)
  • Verify that no errors appear in the JS console

Offline tests

The camera feature is device-local and does not require network connectivity. Taking a photo offline should work normally — the attachment will be queued for upload when connectivity returns.

QA Steps

Same as tests above, performed on:

  • Android native device

  • iOS native device

  • 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.
Checks run
Check Result
Prettier ✅ Pass
ESLint ✅ Pass
TypeScript (tsgo) ✅ Pass
Translation generation ✅ Pass
Jest tests ⏳ Running in CI

Screenshots/Videos

Android: Native
Android: mWeb Chrome

N/A — camera feature is native-only

iOS: Native
iOS: mWeb Safari

N/A — camera feature is native-only

MacOS: Chrome / Safari

N/A — camera feature is native-only, web attachment picker is unchanged

- [ ] I verified that similar component doesn't exist in the codebase - [ ] I verified that all props are defined accurately and each prop has a `/** comment above it */` - [ ] I verified that each file is named correctly - [ ] I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone - [ ] I verified that the only data being stored in component state is data necessary for rendering and nothing else - [ ] In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes - [ ] 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) - [ ] I verified that component 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`) - [ ] I verified that all JSX used for rendering exists in the render method - [ ] I verified that each 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

Screenshots/Videosundefined

Replace the external system camera intent with an in-app VisionCamera
modal for the "Take photo" option in the attachment picker on both
Android and iOS. This keeps Expensify in the foreground during photo
capture, preventing the OS from reclaiming the app's memory.

Addresses deploy blockers from previous implementation:
- Tap-to-focus with animated focus indicator
- ScrollView for permission-denied view in landscape mode
- Safe area insets for camera hole/nav bar/notch handling
- AppState listener to refresh camera after granting permissions
- Camera flip (front/back) support
- Proper modal with supportedOrientations for landscape

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>
@OSBotify
Copy link
Copy Markdown
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 308b3731..677cd78c 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1181,7 +1181,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[de] Let it go',
         dropMessage: '[de] Drop your file here',
         flash: '[de] flash',
-        flipCamera: '[de] Flip camera',
+        flipCamera: 'Kamera drehen',
         multiScan: '[de] multi-scan',
         shutter: '[de] shutter',
         gallery: '[de] gallery',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index ca408514..f92e48d2 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1181,7 +1181,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[fr] Let it go',
         dropMessage: '[fr] Drop your file here',
         flash: '[fr] flash',
-        flipCamera: '[fr] Flip camera',
+        flipCamera: 'Inverser la caméra',
         multiScan: '[fr] multi-scan',
         shutter: '[fr] shutter',
         gallery: '[fr] gallery',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 6dd08737..74d5e357 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1181,7 +1181,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[it] Let it go',
         dropMessage: '[it] Drop your file here',
         flash: '[it] flash',
-        flipCamera: '[it] Flip camera',
+        flipCamera: 'Inverti fotocamera',
         multiScan: '[it] multi-scan',
         shutter: '[it] shutter',
         gallery: '[it] gallery',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 01d09641..12acef6e 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1181,7 +1181,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[ja] Let it go',
         dropMessage: '[ja] Drop your file here',
         flash: '[ja] flash',
-        flipCamera: '[ja] Flip camera',
+        flipCamera: 'カメラを反転',
         multiScan: '[ja] multi-scan',
         shutter: '[ja] shutter',
         gallery: '[ja] gallery',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 6ba55c2f..c44fda45 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1181,7 +1181,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[nl] Let it go',
         dropMessage: '[nl] Drop your file here',
         flash: '[nl] flash',
-        flipCamera: '[nl] Flip camera',
+        flipCamera: 'Camera omdraaien',
         multiScan: '[nl] multi-scan',
         shutter: '[nl] shutter',
         gallery: '[nl] gallery',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 7c85693c..87fca8c6 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1181,7 +1181,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[pl] Let it go',
         dropMessage: '[pl] Drop your file here',
         flash: '[pl] flash',
-        flipCamera: '[pl] Flip camera',
+        flipCamera: 'Odwróć kamerę',
         multiScan: '[pl] multi-scan',
         shutter: '[pl] shutter',
         gallery: '[pl] gallery',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 778625c3..914dce1b 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1183,7 +1183,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[pt-BR] Let it go',
         dropMessage: '[pt-BR] Drop your file here',
         flash: '[pt-BR] flash',
-        flipCamera: '[pt-BR] Flip camera',
+        flipCamera: 'Inverter câmera',
         multiScan: '[pt-BR] multi-scan',
         shutter: '[pt-BR] shutter',
         gallery: '[pt-BR] gallery',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 0f4ab76c..0263b4d6 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1194,7 +1194,7 @@ const translations: TranslationDeepObject<typeof en> = {
         dropTitle: '[zh-hans] Let it go',
         dropMessage: '[zh-hans] Drop your file here',
         flash: '[zh-hans] flash',
-        flipCamera: '[zh-hans] Flip camera',
+        flipCamera: '翻转摄像头',
         multiScan: '[zh-hans] multi-scan',
         shutter: '[zh-hans] shutter',
         gallery: '[zh-hans] gallery',

Note

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

View workflow run

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing Compress SVG check: ran svgo compression on assets/images/camera-flip.svg (408 → 402 bytes). The SVG path data was optimized by svgo's convertPathData plugin.

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing ESLint check: added missing sentryLabel props to all 4 PressableWithFeedback components in AttachmentCamera.tsx (Close, Flash, Shutter, FlipCamera buttons).

The AttachmentCamera component imports react-native-vision-camera which
tries to initialize the native Camera Module at import time. In the Jest
environment there is no native module, causing all test suites that
transitively import AttachmentPicker to fail with
"system/camera-module-not-found".

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing checks: added a Jest mock for react-native-vision-camera in __mocks__/react-native-vision-camera.ts.

The AttachmentCamera component imports react-native-vision-camera which tries to initialize the native Camera Module at import time. In Jest there's no native module available, so every test suite that transitively imports AttachmentPicker (via index.native.tsx) was crashing with system/camera-module-not-found.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

⏱️ Ran out of time before I could finish. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in #melvinbot-ai.

Run details

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing Prettier check: ran prettier --write on __mocks__/react-native-vision-camera.ts which needed multi-line formatting for the Camera object assignment.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

⚠️ MelvinBot CI Fix Loop Detected

MelvinBot has made 5 consecutive commits trying to fix CI failures. Automatic CI fix dispatches are now paused for this PR.

Next steps: A human should review the recent commits and resolve the conflicting CI errors manually.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 10, 2026

Codecov Report

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

Files with missing lines Coverage Δ
...rc/components/Icon/chunks/expensify-icons.chunk.ts 0.00% <ø> (ø)
src/components/AttachmentPicker/index.native.tsx 21.87% <33.33%> (+0.92%) ⬆️
...c/components/AttachmentPicker/AttachmentCamera.tsx 44.11% <44.11%> (ø)
... and 11 files with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants