mapbox / mapbox/mapbox-navigation-android

Get instruction image from onNewBannerInstructions listener

Open
#7,839 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
651
Forks
321
PR merge metrics
No merged PRs in 30d

Description

I am listening to `onNewBannerInstructions` to show the instruction text and image on our custom view, without using any of Mapbox UIs. When `onNewBannerInstructions` is called, I check the components of the primary instruction and the image URL is null. How can I get the image for the instruction?

Screenshot 2024-07-02 at 7 52 25 AM

**Android API:** 34
**Mapbox Navigation SDK version:** com.mapbox.navigationcore:navigation:3.0.2

### Steps to trigger behavior

1. Start a new trip session
2. register banner instructions observer

### Expected behavior

We should be able to extract and use the instruction image from Mapbox Navigation SDK.

### Actual behavior

We are unable to extract and use the instruction image from Mapbox Navigation SDK.

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 with the onNewBannerInstructions observer during a new trip session, then inspect the primary instruction components and their image URL. Done means establishing whether the instruction image can be extracted through the Android Navigation SDK API and documenting or exposing the supported result for custom views.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.