mapbox / mapbox/mapbox-navigation-android
Telemetry distanceremaining should be the estimateddistance when departing
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
**Mapbox Navigation SDK version:** 1.2.0-alpha.2
Discovered this issue here https://github.com/mapbox/mapbox-navigation-android/issues/3682
Mode report here https://app.mode.com/editor/mapbox/reports/69d0cdda2582
The depart event distanceremaining is 0. It should be the estimateddistance, in this example it should have been 4480
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 with the depart telemetry event and compare its distanceremaining value with estimateddistance, using the example and Mode report linked in the issue. Review the related issue #3682 for reproduction context; done means the depart event reports the estimated distance instead of 0 when departing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100