mapbox / mapbox/mapbox-maps-android

Big location pointer on Android Auto

Open
#2,440 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

android auto auto-triaged bug :beetle:
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

![6180b274-e87c-4953-b990-007feccc2f09](https://github.com/user-attachments/assets/52002c38-3b52-45a2-904f-b442549599ba)

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.
![20240709_195037](https://github.com/user-attachments/assets/e808d786-65cb-47f1-a359-af823817c350)

## 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.