Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experimental pointer events conflicting with bottom-sheet gestures #50024

Closed
axyz opened this issue Mar 13, 2025 · 4 comments
Closed

Experimental pointer events conflicting with bottom-sheet gestures #50024

axyz opened this issue Mar 13, 2025 · 4 comments
Labels
Needs: Version Info Resolution: Issue in another tool or repo An issue that was opened against React Native but in reality is affecting another tool or library

Comments

@axyz
Copy link

axyz commented Mar 13, 2025

Description

When experimental pointer events are enabled (https://reactnative.dev/blog/2022/12/13/pointer-events-in-react-native#enable-feature-flags) and a bottom-sheet is closed via touch gestures (https://github.com/gorhom/react-native-bottom-sheet) the pointer events stop working. (issue happens on both Android and iOS)

Honestly not sure where is the issue between

  • react-native experimental pointer events
  • react-native-gesture-handler
  • the bottom sheet implementation

But maybe you may have some ideas and eventually direct me to culprit.

Thanks.

Related: gorhom/react-native-bottom-sheet#2201
Related: software-mansion/react-native-gesture-handler#3445

Steps to reproduce

  1. yarn && yarn android && yarn start
  2. pressing the "press me" pressable increases both the counters for onPressIn as well as onPointerDown events
  3. close the bottom sheet by dragging the handle or the content of the sheet
  4. now pressing "press me" only increases press events, no pointer events are emitted anymore

Note: if the sheet is close with the "close" button, then the issue does not occur

React Native Version

0.78.0

Affected Platforms

Runtime - Android

Areas

Other (please specify)

Output of npx @react-native-community/cli info

$ npx @react-native-community/cli info
info Fetching system and libraries information...
System:
  OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
  CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
  Memory: 7.95 GB / 30.58 GB
  Shell:
    version: "5.9"
    path: /home/axyz/.nix-profile/bin/zsh
Binaries:
  Node:
    version: 22.8.0
    path: ~/.nvm/versions/node/v22.8.0/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v22.8.0/bin/yarn
  npm:
    version: 10.8.3
    path: ~/.nvm/versions/node/v22.8.0/bin/npm
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
Languages:
  Java: Not Found
  Ruby:
    version: 3.0.2
    path: /bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.1
    wanted: 15.0.1
  react:
    installed: 19.0.0
    wanted: 19.0.0
  react-native:
    installed: 0.78.0
    wanted: 0.78.0
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Stacktrace or Logs

no error shown in console

Reproducer

https://github.com/axyz/rn-bug-pointer-events-bottom-sheet

Screenshots and Videos

No response

@axyz axyz added Needs: Triage 🔍 Type: New Architecture Issues and PRs related to new architecture (Fabric/Turbo Modules) labels Mar 13, 2025
@react-native-bot
Copy link
Collaborator

Warning

Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2.

@react-native-bot
Copy link
Collaborator

Warning

Could not parse version: We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.76.2.

@migueldaipre
Copy link
Collaborator

Hey, Thanks for reporting this issue.

It seems like this issue is actually unrelated to React Native core. Please open this issue against this other repository:

https://github.com/gorhom/react-native-bottom-sheet/issues

I'll be closing this but feel free to reopen if the other repo points back to us as a issue in the core of React Native.

also cc @gorhom for visibility

@migueldaipre migueldaipre added Resolution: Issue in another tool or repo An issue that was opened against React Native but in reality is affecting another tool or library and removed Needs: Author Feedback Type: New Architecture Issues and PRs related to new architecture (Fabric/Turbo Modules) labels Mar 18, 2025
@axyz
Copy link
Author

axyz commented Mar 18, 2025

@gorhom for reference I tried to create an issue multiple times, but it always gets automatically closed because it cannot be reproduced using a "snack", I can only provide the github repo to reproduce due to the need for compilation with feature flags enabled. See: gorhom/react-native-bottom-sheet#2204 let me know if I can provide any additional detail or if the issue can be reopened manually

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Version Info Resolution: Issue in another tool or repo An issue that was opened against React Native but in reality is affecting another tool or library
Projects
None yet
Development

No branches or pull requests

3 participants