-
-
Notifications
You must be signed in to change notification settings - Fork 864
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
[Bug]: marker views not propagating press events from their children #3440
Comments
I have a similar issue on iOS, on android it seems to be working normally Also the onPress on MapView, onTouchMove and onTouchEnd don't work, while onTouchStart does On MarkerView, the onPressIn and onPressOut work, but onPress doesn't Seems to be a general event propagation issue on iOS. Also using rnmapbox/maps, version 10.1.11 with default mapbox version, react native version 0.72.6 |
This is only happening on iPhone XS for us. Same for you all? |
A potential solution is to temporarily use |
I am also having this issue on rnmapbox/maps version Simple code example:
|
I'm using |
After checking
So I managed to use |
Why don't we remove that |
Mapbox Implementation
Mapbox
Mapbox Version
10.16.4
React Native Version
0.73.1
Platform
iOS
@rnmapbox/maps
version10.1.19
Standalone component to reproduce
Observed behavior and steps to reproduce
Map shows the child of the MarkerView rendered nicely. However when clicking upon the marker, no event seems to be propagated. No logs come out for the onPress event of the Pressable component used as a child of the MarkerView.
Expected behavior
The console log of 'pressing the marker view' should be seen in the logs. It is not.
Notes / preliminary analysis
I've tried using a PointAnnotation but cannot get an
component from ReactNative to render at all when using that as a child of the PointAnnotation.
Have tried all sorts of things. This is very frustrating. Any help would be greatly, greatly appreciated!
Additional links and references
No response
The text was updated successfully, but these errors were encountered: