[Android] v3 `ReanimatedSwipeable` takes over a vertical scroll in a React Native list once the finger drifts 10 dp sideways

Open
#4,670 6 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@JaydeepAgravat is already working on this.

Since Nov 6, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
android, react-native, typescript
Domain
backend, mobile

Research direction

Start by tracing RNGestureHandlerRootHelper.requestDisallowInterceptTouchEvent() and GestureHandlerOrchestrator.cancelAllLegacyHandlers(), then check how v3 detector action types are handled alongside the deferred cancellation from #4441. Reproduce with the linked example on Android using a vertical drag with sideways drift. Done when the React Native list keeps scrolling without opening a swipeable row, while existing gesture cancellation behavior still works.

Written by the indexing model from the issue text.

Description

Platform: Android
Description

On Android, a ReanimatedSwipeable row inside a React Native FlatList / SectionList / ScrollView can take the touch away from a scroll that has already started. A vertical scroll with any slight sideways drift (a normal thumb arc) gets cancelled, and the row under the finger swipes open instead. iOS doesn't have the problem: once UIScrollView's pan has recognized, the row can't activate.

The cause looks like the same gap as #4432, this time for gestures created with the v3 hooks:

  • When React Native's ScrollView starts dragging, it calls requestDisallowInterceptTouchEvent(true). RNGestureHandlerRootHelper.requestDisallowInterceptTouchEvent() responds with GestureHandlerOrchestrator.cancelAllLegacyHandlers(), which only cancels handlers whose action type is JS_FUNCTION_OLD_API, JS_FUNCTION_NEW_API, REANIMATED_WORKLET or NATIVE_ANIMATED_EVENT.
  • ReanimatedSwipeable now uses usePanGesture with the v3 GestureDetector, so its pan is attached with ACTION_TYPE_NATIVE_DETECTOR. That type isn't in the list above.
  • #4441 added deferred cancellation (cancelHandlersOnNativeTouchGrab), but it only covers NativeViewGestureHandlers that opt in (buttons).

As a result the scroll view's touch grab doesn't cancel the swipeable's pan. The pan keeps tracking for the rest of the scroll and activates as soon as the total horizontal movement passes activeOffsetX (10 dp by default). The root then intercepts and cancels the ScrollView mid-scroll.

The v2 Swipeable and the v2 Gesture.Pan() API didn't have this problem, because their action types are in cancelAllLegacyHandlers, so this is a regression for anyone moving to v3.

Workaround: use gesture-handler's ScrollView as the list's scroll view (renderScrollComponent={(props) => <ScrollView {...props} />}) together with gesture-handler's RefreshControl. The scroll then takes part in the orchestrator's normal arbitration and wins once it's active.

Steps to reproduce
  1. Render a vertical React Native FlatList (not gesture-handler's) of ReanimatedSwipeable rows with renderRightActions.
  2. On an Android device, drag upward about 900 px with roughly 250 px of leftward drift (about 15° off vertical).
  3. The list barely scrolls, and the row under the finger swipes open to its right actions.
  4. Drag straight up the same distance: the list scrolls normally.
  5. Switch the list to gesture-handler's FlatList (or pass gesture-handler's ScrollView via renderScrollComponent) and repeat step 2: the list scrolls and no row opens.
import { FlatList, Text, View } from 'react-native';
import ReanimatedSwipeable from 'react-native-gesture-handler/ReanimatedSwipeable';

const data = Array.from({ length: 50 }, (_, i) => String(i));

export default function App() {
  return (
    <FlatList
      data={data}
      keyExtractor={(item) => item}
      renderItem={({ item }) => (
        <ReanimatedSwipeable
          renderRightActions={() => <View style={{ width: 80, backgroundColor: 'red' }} />}
        >
          <View style={{ height: 72, justifyContent: 'center', padding: 16, backgroundColor: '#eee' }}>
            <Text>Row {item}</Text>
          </View>
        </ReanimatedSwipeable>
      )}
    />
  );
}

Suggested fix: include ACTION_TYPE_NATIVE_DETECTOR (and ACTION_TYPE_VIRTUAL_DETECTOR, if it applies) in the handlers cancelled when a native view grabs the touch mid-gesture, or give them the deferred grabbedMidGesture treatment from #4441.

A link to a Gist, an Expo Snack or a link to a repository based on this template that reproduces the bug.

https://github.com/IGx89/rngh-swipeable-scroll-repro

Gesture Handler version

3.3.0 (code unchanged on main / 3.4.0)

React Native version

0.88.1

Platforms

Android

JavaScript runtime

Hermes

Workflow

Using Expo Prebuild or an Expo development build

Build type

Debug mode

Device

Real device

Device model

Samsung Galaxy XCover Pro (SM-G715U), Android 13

Acknowledgements

Yes

Dominant language
TypeScript
Stars
6.8k
Forks
1.1k
Avg merge
1d 23h
Merged PRs (30d)
46

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from software-mansion/react-native-gesture-handler

All issues in software-mansion/react-native-gesture-handler

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.