[Android] Fix TextInput simultaneous relations

[m-bert]

Description

shouldRecognizeSimultaneously hook method has three possible return values: true/false/null. Override in EditText hook states that:

(...) if other handler is NativeViewGestureHandler then don't override the default implementation

However, instead of null it returns ... && handler !is NativeViewGestureHandler, so there's no way of getting null value, which is used in Native gesture shouldRecognizeSimultaneously method.

Fixes #3520

Test plan

Tested on the following code:

import {
  GestureHandlerRootView,
  ScrollView,
  TextInput,
} from 'react-native-gesture-handler';

function Component() {
  return (
    <ScrollView>
      {Array.from({ length: 50 }).map((_, index) => (
        <TextInput
          key={index}
          placeholder={`${index}`}
          style={{
            height: 40,
            borderColor: 'gray',
            borderWidth: 1,
            marginBottom: 10,
          }}
        />
      ))}
    </ScrollView>
  );
}

export default function App() {
  return (
    <GestureHandlerRootView>
      <Component />
    </GestureHandlerRootView>
  );
}

[Copilot]

Pull request overview

This PR fixes Android TextInput simultaneous-recognition behavior by allowing the EditText hook to return null from shouldRecognizeSimultaneously, so NativeViewGestureHandler can fall back to its default simultaneous-recognition logic when the peer handler is also a NativeViewGestureHandler.

Changes:

• Update EditTextHook.shouldRecognizeSimultaneously to return null when the other handler is NativeViewGestureHandler (instead of always returning a boolean).
• Keep explicit exclusion of RootViewGestureHandler from simultaneous recognition.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.