You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
NavigationMap - Android: When there is a route with many destinations and each destination has a marker on the map, the first marker will not fire the onMarkerClick event. #325
When there is a route with many destinations and each destination has a marker on the map, the first marker will not fire the onMarkerClick event.
Environment details
Library version and other environment information:
react-native-navigation-sdk version: 0.6.1
OS type and version
iOS: 18.1, 18.0
Android: 35
Steps to reproduce
Pull down this branch.
Install the dependencies.
Run yarn start
Run yarn ios or yarn android
Click on navigate button
When the map, route and markers are load click on each of the markers. You should see a log in the console firing onMarkerClick. On iOS this works as expected and the onMarkerClick will fire.
On Android, click on the first marker or marker.id of "m0" and the onMarkerClick will not fire, however all the other markers will fire the onMarkerClick.
The problem is that when marker that is over the currently active route leg is clicked, the event is captured by the SDK (for route leg click handling) and is not propagated to the marker click listener.
As this package is just a wrapper for Navigation SDK for Android and iOS platforms, only features available on the SDK can and should be implemented to the plugin itself.
I will continue investigating if there is possiblity to control how route click events are handled, but this might not be possible with current Navigation SDK version for Android.
Activity
jokerttu commentedon Nov 4, 2024
Thanks for reporting this issue!
rhinkle commentedon Nov 4, 2024
I was able to trigger the m0 marker for Android clicking around/within the gray dot.
caio1985 commentedon Nov 26, 2024
@jokerttu Can you please take a look?
jokerttu commentedon Nov 28, 2024
Hi,
I was able to reproduce this issue,
The problem is that when marker that is over the currently active route leg is clicked, the event is captured by the SDK (for route leg click handling) and is not propagated to the marker click listener.
As this package is just a wrapper for Navigation SDK for Android and iOS platforms, only features available on the SDK can and should be implemented to the plugin itself.
I will continue investigating if there is possiblity to control how route click events are handled, but this might not be possible with current Navigation SDK version for Android.