mapbox / mapbox/mapbox-maps-android
Location puck not moving
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: ested on Android 14, Android 16 and Android 10
- Devices affected:Samsung phones
- Maps SDK Version: android-ndk27:11.17.1
## Observed behavior and steps to reproduce
The location puck is not updating as frequent as expected.
We have a service that records user location and draws the location update points on a map layer.
Looking at the map we can see that the location puck "follows" the same location updates that we receive from background service when the user is moving.
Now in version 11, in some cases, the puck just remains stopped in the map (both when app has connectivity or not) even knowing the user is moving and the phone is receiving location updates that are drawn on map layer.
## Expected behavior
The puck should move when the user is moving and be up to date with the last known user location.
## Notes / preliminary analysis
in our app we use the addOnIndicatorPositionChangedListener and addOnIndicatorBearingChangedListener
## Additional links and references
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 by reproducing the stopped location puck on the listed Android versions and Samsung devices while observing addOnIndicatorPositionChangedListener and addOnIndicatorBearingChangedListener alongside the app's received location updates. Done means identifying why the puck stops despite new updates and confirming that it follows the latest known location while moving, both online and offline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100