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.
This ticket is to report a mismatch between the camera target and the actual device location, when the Mapbox China Plugin for Android is being used and the LocationComponent is in TRACKING camera mode.
@LukasPaczos ' comments about this from a conversation elsewhere:
The shifter will translate all of the GeoJSON shapes (Point objects), that's why the puck is rendered at the correct place, but it won't impact the camera position (LatLng objects).
that Point.fromLngLat(latLng.getLongitude(), latLng.getLattitude()) is an often practice, which would result in double shifting. We should probably introduce the shifting whenever a raw LatLng is passed to core instead, which means a lot of entry points though.
This ticket is to report a mismatch between the camera target and the actual device location, when the Mapbox China Plugin for Android is being used and the
LocationComponent
is inTRACKING
camera mode.Steps to reproduce
LocationComponent
with theTRACKING
camera mode.Expected behavior
The camera stays directly centered on the device location puck.
Actual behavior
The camera target location has a mismatch with the device's location (puck).
Configuration
Android versions: Pie
Device models: OnePlus 5
Mapbox SDK versions: 8.0.0
The text was updated successfully, but these errors were encountered: