mapbox / mapbox/mapbox-navigation-android
AndroidAuto navigation seems to be ignoring driver position
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
I'm currently using MapBox with AndroidAuto in Australia where the driver position is on the right. For things like google maps this means that the cards are usually displayed on the right, closest to the driver. But for some reason this isn't being respected and the cards in AndroidAuto still display on the left side. Is this something MapBox has control over at all? This doesn't seem to be an issue in CarPlay in the iOS implementation but it is for AndroidAuto for some reason.
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 at the AndroidAuto integration and reproduce the navigation-card placement with a right-hand-drive setup in Australia. Determine whether Mapbox controls the card side or AndroidAuto does; done means identifying the controlling component and documenting or fixing the behavior if it is within this SDK.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100