mapbox / mapbox/mapbox-navigation-android
Custom DirectionsRoute still counts as an "Active Guidance Trip"
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
**Android API:** `MapboxNavigation.setNavigationRoutes()`
**Mapbox Navigation SDK version:** 2.14.0
### Steps to trigger behavior
1. Load a DirectionsRoute from your own Routing Server
2. Set route via `MapboxNavigation.setNavigationRoutes()`
3. Start trip session via `MapboxNavigation.startTripSession()`
### Expected behavior
Not counting towards "Active Guidance Trips" statistics and we get billed for it.
### Actual behavior
Counting towards "Active Guidance Trips" statistics and we get billed for it.
My questions are:
* How can we skip the "Active Guidance Trip" statistics?
* What does an "Active Guidance Trip" entail that necessitates for us to get billed for it?
We do compute our own routes, because we have a use case that is tailored to a very specific way of routing that is not supported by Mapbox
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 tracing the behavior of MapboxNavigation.setNavigationRoutes() and MapboxNavigation.startTripSession() for routes loaded from an external routing server. Determine how this flow affects Active Guidance Trip statistics and billing, then define the supported behavior or limitation and verify it with the relevant Android SDK tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100