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 }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
@klblk could you try testing with the latest SNAPSHOT? We made some changes since the last beta, I'm trying to pinpoint if the root cause will be different from #6762.
a) The issue that LatLngBounds returns a wrong bounding box is noted in #6769, this is because we changed the way the OnMapReadyCallback is invoked and at that time the View isn't measured yet. To workaround this I would advice you to wrap it in a runnable or use addOnGlobalLayoutListener. We are working on including this as a requirement to invoke the OnMapReady but this will only land as part of the 5.0.0 release since it requires some internal refactoring.
b) The issue in #6762 will be the same as shown here. Going to use that issue to investigate.
Since both issues are tracked elsewhere, going to close as duplicate.
Thanks again for reaching out and reporting your issue!
Platform: Android
Mapbox SDK version: 4.2.0-beta5
Steps to trigger behavior
a) getLatLngInBounds() returns an incorrect result. Problem in mapboxMap.getProjection().getVisibleRegion().latLngBounds value:
b) Animated markers blinking if the camera shift (sorry, I'm bad gif-maker):

c) #6422 actual (if change MarkerViewOptions to MarkerOptions passengerMarker)
The text was updated successfully, but these errors were encountered: