mapbox / mapbox/mapbox-maps-android
Big location pointer on Android Auto
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: 14, 13
Devices affected: SM-S908B, SM-S901B
Maps SDK Version: 10.16.6-SNAPSHOT.0306T1139Z.764ecaa
## Observed behavior and steps to reproduce
Users are facing issue of seeing big location pointer on android auto randomly when opening the app. This goes away when they switch to some another app and then come back

https://github.com/user-attachments/assets/2aa45b2c-3598-43ce-8c85-1d5826db832b
## Expected behavior
The pointer should be shown in a small size as is normally displayed.

## Notes / preliminary analysis
We followed the same step to add the location puck as mentioned in the documentation but still the issue does seem to occur randomly. Have added the code below of how we are adding the location puck
mapboxMap?.getStyle {
val drawable = ContextCompat.getDrawable(context, R.drawable.mapbox_user_puck_icon)
surface?.mapSurface?.location2?.updateSettings2 {
puckBearingEnabled = true
puckBearingSource = COURSE
}
surface?.mapSurface?.location?.locationPuck = LocationPuck2D(bearingImage = drawable)
}
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 issue on Android Auto with Android 13 or 14 and the affected Samsung devices, using the documented location puck setup shown in the report. Compare the randomly oversized pointer with the normal display when switching away from and back to the app. Done means the location pointer consistently remains at its expected small size when opening the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100