mapbox / mapbox/mapbox-navigation-android
Android Drop-In UI: Allow the user to continue his navigation even after he reaches his destination.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I am using DropInUI for my application. I saw the navigation stops navigating further once the user reaches the destination. For example, If the driver passed his destination by mistake then the navigation should reroute the driver to the destination again. I think the dropInUi is not working in that way right now. Sometimes if the drivers passed the destination then there is no way he can navigate to his destination again. The only way is he should close and restart the navigation.
**Android 10**
**implementation 'com.mapbox.navigation:ui-app:2.8.0-beta.2'
implementation 'com.mapbox.navigation:ui-dropin:2.8.0-beta.2'**
### Steps to trigger behavior
1. Start the navigation to any destination
2. Reach the destination
3. The active navigation stops automatically and the maneuver instruction,speed,sound, overview and recenter button will go away.
### Expected behavior
The navigation should continue until the driver tap x(cancel) button in the infopanel.
### Actual behavior
It stops the navigation.
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 behavior with Android Drop-In UI 2.8.0-beta.2 using the listed steps: reach a destination and observe the active navigation state. Inspect the DropInUI destination-arrival flow and verify that navigation remains active until the info-panel cancel button is tapped, including rerouting after the driver passes the destination.
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
- 35/100