Skip to content

Migrate attachment carousel and MultiGestureCanvas gestures to Gesture Handler 3 hooks - #103461

Merged
mountiny merged 13 commits into
Expensify:mainfrom
software-mansion-labs:collectioneur/gesture-handler-hooks-attachments
Oct 23, 2026
Merged

mountiny merged 13 commits into
Expensify:mainfrom
software-mansion-labs:collectioneur/gesture-handler-hooks-attachments

Conversation

@collectioneur

@collectioneur collectioneur commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Part of the migration from the deprecated Gesture Handler 3 builder API (Gesture.*, GestureType, Legacy* types) to the hook API (#102782). The migration is split into independent PRs by feature area. This one covers the attachment carousel and MultiGestureCanvas.

Mechanical changes: Gesture.*() builders → use*Gesture() hooks, onStart/onChange/onEnd → onActivate/onUpdate/onDeactivate, state.activate()/fail() → GestureStateManager.activate()/fail(evt.handlerTag), success in onFinalize → !event.canceled.

Non-obvious parts:

  • No gesture refs in the hook API. Relations take gesture objects, so the web carousel passes its pan through the pager context as pagerGesture (used by Lightbox, PDFView, MultiGestureIcon). pagerRef now only tells an attachment it's inside a carousel. On native it never carried a real relation (PagerView has no handlerTag).
  • Creation order in MultiGestureCanvas. A gesture can only reference gestures created before it, so the pan is created first and the taps declare the simultaneous relation with it (simultaneous relations are symmetric). The relations and the Simultaneous(pinch, Race(taps, pan)) composition are unchanged.
  • Local hooks renamed. usePanGesture / usePinchGesture / useTapGestures in MultiGestureCanvas are now useCanvasPanGesture / useCanvasPinchGesture / useCanvasTapGestures, so they no longer shadow the Gesture Handler hooks. The Gesture Handler hooks are called by their own names, and the worklets Babel plugin turns their callbacks into worklets automatically (checked on the transformed native output: all 14 callbacks are worklets).
  • React Compiler. Without refs read during render, MultiGestureCanvas and AttachmentCarouselView now compile with both Babel and OXC, so the React.memo workaround on AttachmentCarouselView is removed.

Fixed Issues

$ #102782
PROPOSAL: N/A

Tests

iOS/Android:

  1. Open a chat with several image attachments and open one.
  2. Pinch to zoom and verify it zooms around the fingers and bounces back past the limits.
  3. While zoomed, pan in all directions and verify the image follows the finger, keeps moving after a fling, snaps back inside the bounds, and a horizontal swipe pans instead of switching attachments.
  4. Double tap a point to zoom in around it and double tap again to zoom out. Not zoomed, swipe left / right to switch attachments (a short slow swipe snaps back).

iOS/Android:

  1. Tap + in the Concierge box on Home and pick two images and a .txt file at once. In the preview, verify swiping switches between the files.

IOS/Android:

  1. Outside the carousel and with a mouse: open a user's avatar full screen, and expand a chart from a chat message (e.g. a Concierge reply with a chart). Pinch, pan, double tap and swipe down, and verify each works.

Android:

  1. PDFs and non-previewable files: open a PDF in a carousel with other attachments.
  2. Verify vertical scrolling doesn't switch attachments, a horizontal swipe does, and once the PDF is zoomed horizontal swipes no longer switch.

Web:
4. open an image attachment with siblings and verify the arrows and the keyboard arrow keys switch attachments.

Note: pinch freezing at the max/min zoom on Android is a known bug on main (#103648), not caused by this PR.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that 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 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)
  • 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)
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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
android_attachment_compressed.mp4
Android: mWeb Chrome
Screen.Recording.2026-10-22.at.15.46.34.mov
iOS: Native
ios_attachmentCarousel_compressed.mp4
iOS: mWeb Safari

Uploading Screen Recording 2026-10-22 at 15.32.39.mov…

MacOS: Chrome / Safari
web_attachment.mov

…e Handler 3 hooks

Move the attachment carousel (web pan and native pager), the Android PDF
pager pan and MultiGestureCanvas (pinch, pan, single and double tap) from
the deprecated builder API to the hook API.

Gesture refs don't exist in the hook API, so the web carousel passes its
pan gesture through the pager context as pagerGesture instead of the
gesture ref in pagerRef. pagerRef now points to the pager itself and only
tells the attachment it is rendered inside a carousel. In
MultiGestureCanvas the pan gesture is created before the taps, because
the single tap waits for it to fail; the taps declare the simultaneous
relation with the pan instead, which is symmetric.

Without the refs read during render, AttachmentCarouselView and
MultiGestureCanvas now compile with React Compiler, so the React.memo
workaround is dropped and the seatbelt baseline is tightened.
@codecov

codecov Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

@collectioneur

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-16T16:44:31.487470Z 14f6eec Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: 6cc35c615a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@collectioneur
collectioneur marked this pull request as ready for review October 16, 2026 16:25
@collectioneur
collectioneur requested review from a team as code owners October 16, 2026 16:25
@melvin-bot
melvin-bot Bot requested review from QichenZhu and removed request for a team October 16, 2026 16:25
@melvin-bot

melvin-bot Bot commented Oct 16, 2026

Copy link
Copy Markdown

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

@melvin-bot
melvin-bot Bot requested review from JmillsExpensify and removed request for a team October 16, 2026 16:25

@mikolajpochec mikolajpochec left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM! I'm leaving two comments. Nothing blocking

Comment thread src/components/Attachments/AttachmentCarousel/AttachmentCarouselView/index.tsx Outdated
Comment thread src/components/MultiGestureCanvas/useCanvasPinchGesture.ts Outdated

@JmillsExpensify JmillsExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No product review required.

@collectioneur

Copy link
Copy Markdown
Contributor Author

@QichenZhu could you please test this one too? 🙏

@QichenZhu

This comment was marked as resolved.

@MelvinBot

Copy link
Copy Markdown
Contributor

I found no accessibility issues in this PR. It only changes how the gestures are wired up (the Gesture Handler 3 hook API). It does not touch any accessibility labels, roles, focus order, keyboard handling, or the carousel arrow buttons.

What I checked
  • No accessibility props changed. None of the 13 changed files add, remove, or change accessibilityLabel, role, accessible, focus, or keyboard handlers. The carousel arrows and arrow-key navigation are untouched in AttachmentCarouselView/index.tsx:247-266.
  • Arrow visibility on tap behaves the same. The single tap toggles the arrows (the main non-gesture way to switch attachments). It now checks evt.canceled instead of !success in useCanvasTapGestures.ts:183. In react-native-gesture-handler 3.3.0, canceled is true for both the FAILED and CANCELLED states. That matches the old success flag, so failed taps still don't toggle the arrows.
  • Carousel detection on web still works. pagerRef now points to scrollRef on web. PDFView still gets a truthy isUsedInCarousel from it.
  • The gesture setup is unchanged. The composition (Simultaneous(pinch, Race(taps, pan))) and the enabled: canUseTouchScreen guard on the web pan are the same as before. Screen-reader users don't trigger these gestures directly, because VoiceOver and TalkBack handle touches first.

Already on main (not caused by this PR): Pinch-to-zoom and double-tap-to-zoom have no button alternative, as WCAG 2.5.1 (Pointer Gestures) asks. Attachment switching does have one: the arrows and the arrow keys.

I reviewed only the code. I didn't run the changes in the app.

@QichenZhu

QichenZhu commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

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
    https://expensify.slack.com/archives/C049HHMV9SM/p1764642854883869
  • I verified any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • 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)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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
android-native.mp4
android-native.webm
Android: mWeb Chrome
android-web.mp4
android-web.webm
iOS: HybridApp
ios-native.mp4
ios-native.mov
iOS: mWeb Safari
ios-web.mp4
ios-web.mov
MacOS: Chrome / Safari
mac-web.mov

@QichenZhu

Copy link
Copy Markdown
Contributor

NAB: on Android mWeb, in a chat with at least two image attachments, open the second one, double tap to zoom in, then immediately swipe right. The carousel stops responding to tapping and panning.

nab-1.mov

@QichenZhu

Copy link
Copy Markdown
Contributor

NAB: on Android mWeb, you need to swipe right on a PDF several times to switch to the previous attachment.

nab-2.webm

QichenZhu

This comment was marked as resolved.

@QichenZhu

Copy link
Copy Markdown
Contributor

Please let me know when this is ready for re-review.

@collectioneur

Copy link
Copy Markdown
Contributor Author

@QichenZhu, the PR is ready for re-review. The problem was that the new hooks API changed the order of applying gestures on the web, which is why the Pan onDeactivated wasn't applied on mWeb iOS. The fix was to declare pitch before pan, and now everything works. I also added videos for mWeb iOS and Android 😄

@QichenZhu QichenZhu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks!

@melvin-bot
melvin-bot Bot requested a review from mountiny October 23, 2026 04:12

@mountiny mountiny left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks

@mountiny
mountiny merged commit dd8a925 into Expensify:main Oct 23, 2026
36 of 38 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
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.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.5.20-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update is needed. This PR is an internal migration of attachment carousel and zoom gestures to the Gesture Handler 3 hook API, and it doesn't change any feature, label, or workflow that users see.


view run

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