fix: use in-app VisionCamera for chat attachments on Android and iOS (v2) by MelvinBot · Pull Request #86621 · Expensify/App

MelvinBot · 2026-03-29T13:29:00Z

Explanation of Change

On Android, tapping "Take photo" in the chat attachment picker launches the system camera via an external intent, which backgrounds the Expensify app. When the OS is under memory pressure, it can reclaim Expensify's process while the system camera is active — particularly during post-capture processing when memory usage spikes. This causes a crash when the user returns from the camera.

This PR replaces the external camera intent with an in-app camera modal powered by react-native-vision-camera (VisionCamera), which is already used in the receipt scan flow (IOURequestStepScan). By keeping Expensify in the foreground during photo capture, we eliminate the window in which the OS can reclaim the app's memory. The in-app camera is used on both Android and iOS for a consistent experience.

Changes:

New AttachmentCamera component (AttachmentCamera.tsx): A full-screen modal with VisionCamera viewfinder, shutter button, flash toggle, and back button. Handles camera permissions using the same CameraPermission module already used by receipt scan.
Modified AttachmentPicker/index.native.tsx: The "Take photo" menu item now opens the in-app camera modal instead of launching the external system camera on both Android and iOS. The captured photo flows through the same pickAttachment processing pipeline (resize, validation, upload) as before.

Fixed Issues

$ #84018

Tests

Open the Expensify app on an Android device
Navigate to any chat
Tap the + button, then "Add attachment" → "Take photo"
Verify an in-app camera opens (full screen with viewfinder, shutter button, flash toggle, and back arrow)
Take a photo by tapping the shutter button
Verify the photo is attached to the chat and can be sent successfully
Repeat and close the camera using the back arrow without taking a photo
Verify the attachment flow is properly cancelled (no photo attached)
On an iOS device, repeat steps 2-8 and verify the same in-app camera behavior

Verify that no errors appear in the JS console

Offline tests

Put the device in airplane mode
Open any chat, tap + → "Add attachment" → "Take photo"
Verify the in-app camera opens and a photo can be captured
Verify the photo is queued for upload (optimistic update) and sends once connectivity returns

QA Steps

On an Android device, open any chat
Tap + → "Add attachment" → "Take photo"
Verify the in-app camera appears with viewfinder, shutter button, flash toggle, and back button
Take a photo and verify it attaches to the chat correctly
Try toggling flash on/off and verify it works
Close the camera without taking a photo and verify the flow cancels cleanly
On an iOS device, repeat steps 2-6 and verify the same in-app camera behavior
Verify no errors appear in the JS console throughout

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

On Android, tapping "Take photo" in the attachment picker launches the system camera intent, which backgrounds Expensify. The OS can reclaim the app's memory during post-capture processing, causing a crash when returning from the camera. Replace the external camera intent with an in-app VisionCamera modal on Android. This keeps Expensify in the foreground during photo capture, eliminating the memory reclaim window. The change only affects Android; iOS continues to use the existing external camera. Fixed Issues: #84018 Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

The AttachmentCamera component imports react-native-vision-camera which tries to initialize native modules that don't exist in the Jest test environment. This causes all test suites to fail with "system/camera-module-not-found" error. Add a mock similar to other native module mocks in the jest setup file. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Remove the Platform.OS === 'android' gate so the in-app camera is used on iOS as well, instead of falling back to the external system camera. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Replace the empty spacer in the bottom control bar with a camera flip button using the Rotate icon. Adds cameraPosition state to toggle between 'back' and 'front' devices via useCameraDevice. Flash visibility automatically adapts since front cameras typically lack a flash (already handled by the hasFlash check). Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

The camera view was rendering behind the status bar because the viewfinder container had no top padding. Add paddingTop using the safe area inset so the camera content starts below the status bar. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

The back arrow overlay on the camera viewfinder is not needed. The modal can still be dismissed via the Android hardware back button (onRequestClose). Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

jest-expo auto-mocks NativeModulesProxy functions to async () => {}, which returns undefined. When getCurrentPosition accesses foregroundPermissionResponse.status, it crashes with TypeError. This adds a proper expo-location mock returning valid PermissionResponse objects. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

The jest.mock('expo-location', factory) in jest/setup.ts does not reliably intercept module imports in the test file's module sandbox with the jest-expo preset. The added await waitForBatchedUpdatesWithAct() triggers a getCurrentPosition call that crashes when expo-location's requestForegroundPermissionsAsync() returns undefined from the jest-expo auto-mock. Adding the mock directly in the test file ensures it is hoisted and applied within the test's module sandbox. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

The global expo-location mock in jest/setup.ts was overriding the jest-expo auto-mock, causing Accuracy named imports to resolve as undefined across 40+ test suites. Removed the global mock so jest-expo handles expo-location auto-mocking as before, and added the Accuracy enum to the local mock in IOURequestStepConfirmationPageTest. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

The recent merge of main introduced GPS tracking code that imports from expo-location, whose native module is unavailable in Jest. This caused 40+ test suites to fail at module load time. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Add the provided camera-flip SVG asset and use it in the AttachmentCamera component instead of the generic Rotate icon. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Uses the standard HeaderWithBackButton component in normal document flow above the camera viewfinder, consistent with how other screens handle back navigation. Safe area top padding moved to the outer container so the header sits below the status bar. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

The ActivityIndicator component on main requires the reasonAttributes prop for skeleton span telemetry. This commit adds the prop to the AttachmentCamera usage and reverts the accidental change that made reasonAttributes optional in the type definition. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Remove extra changes that modified REPORT_VIOLATIONS handling — these are unrelated to the in-app camera feature. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

…pture, handleCameraClose Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

melvin-bot · 2026-03-29T13:29:06Z

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

MelvinBot · 2026-03-29T13:45:30Z

I checked the current PR diff and there are no files under types/onyx in the changed files list. Here are all the files currently changed in this PR:

assets/images/camera-flip.svg
jest/setup.ts
src/CONST/index.ts
src/components/AttachmentPicker/AttachmentCamera.tsx
src/components/AttachmentPicker/index.native.tsx
src/components/Icon/chunks/expensify-icons.chunk.ts
src/languages/de.ts
src/languages/en.ts
src/languages/es.ts
src/languages/fr.ts
src/languages/it.ts
src/languages/ja.ts
src/languages/nl.ts
src/languages/pl.ts
src/languages/pt-BR.ts
src/languages/zh-hans.ts

Could you double-check which files you'd like reverted? It's possible the types/onyx changes were already removed in a previous commit.

ShridharGoel · 2026-03-29T13:49:36Z

jest/setup.ts

+// Mock expo-location — the native ExpoLocation module is unavailable in Jest
+jest.mock('expo-location', () => ({
+    Accuracy: {Lowest: 1, Low: 2, Balanced: 3, High: 4, Highest: 5, BestForNavigation: 6},
+    PermissionStatus: {GRANTED: 'granted', UNDETERMINED: 'undetermined', DENIED: 'denied'},
+    getCurrentPositionAsync: jest.fn(),
+    requestForegroundPermissionsAsync: jest.fn(() => Promise.resolve({status: 'granted', granted: true, canAskAgain: true, expires: 'never'})),
+    requestBackgroundPermissionsAsync: jest.fn(() => Promise.resolve({status: 'granted', granted: true, canAskAgain: true, expires: 'never'})),
+    getForegroundPermissionsAsync: jest.fn(() => Promise.resolve({status: 'undetermined', granted: false, canAskAgain: true, expires: 'never'})),
+    getBackgroundPermissionsAsync: jest.fn(() => Promise.resolve({status: 'undetermined', granted: false, canAskAgain: true, expires: 'never'})),
+    hasStartedLocationUpdatesAsync: jest.fn(() => Promise.resolve(false)),
+    startLocationUpdatesAsync: jest.fn(() => Promise.resolve()),
+    stopLocationUpdatesAsync: jest.fn(() => Promise.resolve()),
+    hasServicesEnabledAsync: jest.fn(() => Promise.resolve(true)),
+    reverseGeocodeAsync: jest.fn(() => Promise.resolve([])),
+}));


@MelvinBot revert these 'expo-location' changes

codecov · 2026-03-29T13:50:59Z

Codecov Report

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

Files with missing lines	Coverage Δ
src/CONST/index.ts	`95.20% <ø> (ø)`
...rc/components/Icon/chunks/expensify-icons.chunk.ts	`0.00% <ø> (ø)`
src/components/AttachmentPicker/index.native.tsx	`21.55% <28.57%> (+0.79%)`	⬆️
...c/components/AttachmentPicker/AttachmentCamera.tsx	`2.50% <2.50%> (ø)`
... and 7 files with indirect coverage changes

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

MelvinBot · 2026-03-29T13:51:33Z

Reverted the expo-location mock from jest/setup.ts (removed the 16-line jest.mock('expo-location', ...) block). The react-native-vision-camera mock remains intact.

ShridharGoel · 2026-03-29T13:52:01Z

@MelvinBot remove the first line under "Explanation of change" in the description

MelvinBot · 2026-03-29T13:53:35Z

Done — removed the first line ("This PR is a clean subset of...") from the Explanation of Change section.

ShridharGoel · 2026-03-29T14:51:54Z

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
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-20.at.2.35.16.AM.mov

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

srikarparsi · 2026-03-30T07:48:50Z

Triggering an Ad Hoc build to test

github-actions · 2026-03-30T07:50:11Z

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

joekaufmanexpensify

Good for product

github-actions · 2026-03-30T22:37:38Z

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

github-actions · 2026-03-30T22:42:54Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-8f567bf-be4802b-ee40ea1f1647958a2db7978f8253cecd32c85d1e/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-8f567bf-be4802b-3718b820c6112e0bbc311e1b3d3a2cbfb1fd1d53/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-30T22:44:50Z

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

OSBotify · 2026-03-31T20:05:20Z

🚀 Deployed to staging by https://github.com/srikarparsi in version: 9.3.51-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-03-31T20:08:13Z

👋 I reviewed the changes in this PR against all help site articles under docs/articles/.

Summary

No help site changes are required for this PR.

Analysis

This PR replaces the external system camera intent with an in-app VisionCamera modal for the "Take photo" option in the chat attachment picker on mobile (Android & iOS). Here's what I found after reviewing all relevant articles:

Chat documentation

The main article covering chat attachments — Chat-Features-and-Moderation-Tools.md — describes the mobile attachment flow generically:

"Use the message bar to type a message, add an attachment, or insert an emoji."

It does not reference "Take photo," camera behavior, or the system camera specifically. The user-facing flow (tap + → Add attachment → Take photo) remains the same — only the underlying camera implementation changed (system camera → in-app camera). The existing documentation is accurate at its current level of abstraction.

Receipt scanning documentation

Articles like Create-an-Expense.md, Track-Expenses.md, Track-Personal-Expenses.md, and Attach-and-edit-receipts-on-expenses.md reference camera usage for SmartScan/receipt capture. These already use VisionCamera and are not affected by this PR, which only changes the chat attachment "Take photo" flow.

Conclusion

Since the user-facing action ("Take photo" in the attachment picker) didn't change — only the camera implementation behind it did — no documentation updates are needed.

Julesssss · 2026-04-01T22:25:34Z

PR was reverted to resolve blocker here

OSBotify · 2026-04-02T19:56:24Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.3.51-10 🚀

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

MelvinBot and others added 20 commits March 29, 2026 13:27

Fix: add sentryLabel props to Pressable components in AttachmentCamera

cd7a480

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Use in-app VisionCamera on both Android and iOS

490a9bd

Remove the Platform.OS === 'android' gate so the in-app camera is used on iOS as well, instead of falling back to the external system camera. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Remove back arrow close button from camera view

9e54657

The back arrow overlay on the camera viewfinder is not needed. The modal can still be dismissed via the Android hardware back button (onRequestClose). Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Fix: add Accuracy enum to expo-location mock in jest setup

77d16ea

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Revert unrelated test changes to IOURequestStepConfirmationPageTest

67758b9

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Use custom CameraFlip icon for camera flip button

d9dbcff

Add the provided camera-flip SVG asset and use it in the AttachmentCamera component instead of the generic Rotate icon. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Fix: compress SVG and format with Prettier

2e1a94f

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Revert unrelated changes to ReportUtils.ts and reportAttributes.ts

9d61c41

Remove extra changes that modified REPORT_VIOLATIONS handling — these are unrelated to the in-app camera feature. Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Use CONST.RECEIPT.PHOTO_ASPECT_RATIO for camera aspect ratio

9ed186d

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

Remove unnecessary useCallback from launchInAppCamera, handleCameraCa…

60d7999

…pture, handleCameraClose Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

MelvinBot requested review from a team as code owners March 29, 2026 13:29

MelvinBot assigned ShridharGoel Mar 29, 2026

melvin-bot bot requested review from ShridharGoel and joekaufmanexpensify and removed request for a team March 29, 2026 13:29

melvin-bot bot removed the request for review from a team March 29, 2026 13:29

MelvinBot mentioned this pull request Mar 29, 2026

fix: use in-app VisionCamera for chat attachments on Android and iOS #84770

Closed

64 tasks

ShridharGoel reviewed Mar 29, 2026

View reviewed changes

Revert expo-location mock from jest/setup.ts

0882c50

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>

ShridharGoel approved these changes Mar 29, 2026

View reviewed changes

melvin-bot bot requested a review from srikarparsi March 29, 2026 14:54

srikarparsi added the Ready To Build label Mar 30, 2026

This comment has been minimized.

Sign in to view

joekaufmanexpensify approved these changes Mar 30, 2026

View reviewed changes

srikarparsi merged commit 8f567bf into main Mar 30, 2026
41 of 44 checks passed

srikarparsi deleted the claude-useVisionCameraForAttachments-v2 branch March 30, 2026 22:37

OSBotify mentioned this pull request Mar 31, 2026

Deploy Checklist: New Expensify 2026-03-31 #86774

Closed

OSBotify mentioned this pull request Apr 1, 2026

Android - Attachment - Front camera flash is supported on iOS but not on Android #86853

Closed

7 tasks

MelvinBot mentioned this pull request Apr 1, 2026

Android & iOS - Attachment - No permission prompt when tapping on capture button #86852

Closed

7 tasks

Julesssss mentioned this pull request Apr 1, 2026

Revert "fix: use in-app VisionCamera for chat attachments on Android and iOS (v2)" #86902

Merged

50 tasks

ShridharGoel mentioned this pull request Apr 2, 2026

[Due for Payment 2026-04-09][$250] Android - Attachment - App crashes after taking a photo #84018

Open

7 tasks

MelvinBot mentioned this pull request Apr 2, 2026

fix: use in-app VisionCamera for chat attachments with proper permission handling #86981

Merged

62 tasks

Conversation

MelvinBot commented Mar 29, 2026 • edited by srikarparsi Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 29, 2026

Uh oh!

MelvinBot commented Mar 29, 2026

Uh oh!

ShridharGoel Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

codecov bot commented Mar 29, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

MelvinBot commented Mar 29, 2026

Uh oh!

ShridharGoel commented Mar 29, 2026

Uh oh!

MelvinBot commented Mar 29, 2026

Uh oh!

ShridharGoel commented Mar 29, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

srikarparsi commented Mar 30, 2026

Uh oh!

github-actions bot commented Mar 30, 2026

Uh oh!

This comment has been minimized.

joekaufmanexpensify left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Mar 30, 2026

Uh oh!

github-actions bot commented Mar 30, 2026

Uh oh!

OSBotify commented Mar 30, 2026

Uh oh!

OSBotify commented Mar 31, 2026

Uh oh!

MelvinBot commented Mar 31, 2026

Summary

Analysis

Chat documentation

Receipt scanning documentation

Conclusion

Uh oh!

Julesssss commented Apr 1, 2026

Uh oh!

OSBotify commented Apr 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

MelvinBot commented Mar 29, 2026 •

edited by srikarparsi

Loading

codecov bot commented Mar 29, 2026 •

edited by github-actions bot

Loading