mapbox / mapbox/mapbox-maps-android
Satellite imagery jitter with FollowPuckViewportState
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 578
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
## Environment
- Android OS version: 16
- Devices affected: Google Pixel 10 Pro, Samsung Galaxy Tab A9+, Pixel Tablet emulator
- Maps SDK Version: 11.22.0
## Observed behavior and steps to reproduce
When following the location puck (either real user location or simulated location) using `MapViewportState.transitionToFollowPuckState()` on a map using the `MapboxStandardSatelliteStyle` the satellite imagery is jittering/shaking behind the road network, labels etc. Minimal reproducible example available at https://github.com/danielkvist/mapbox-satellite-jitter-sample producing the following result:
https://github.com/user-attachments/assets/17e7a662-5200-4ca1-935e-99c9b02018a2
## Expected behavior
The satellite imagery should move smoothly together with road network, labels etc.
## Notes / preliminary analysis
The jitter appears approximately between zoom levels 13.5 and 16.5 with varying intensity.
It occurs with `ComposeMapInitOptions.textureView` set to both `true` and `false`.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal reproducible example at https://github.com/danielkvist/mapbox-satellite-jitter-sample and reproduce the issue using MapViewportState.transitionToFollowPuckState() with MapboxStandardSatelliteStyle. Compare behavior across zoom levels 13.5–16.5 and with ComposeMapInitOptions.textureView set to true and false; done means satellite imagery moves smoothly with the road network and labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100