mapbox / mapbox/mapbox-navigation-android
[Bug]: Not seeing the waypoints while adding in RouteOptions.builder() .coordinatesList(originPoint,waypoints,destination) in Android
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
mapboxsdk:mapbox-android-sdk:9.6.1
### Steps to reproduce
When waypoints are added, route map is not loading up
val waypoints = listOf(
Point.fromLngLat(7.4102783203125, 49.7419738769531),
Point.fromLngLat(8.46015930175781, 50.1539611816406)
)
val routeBuilder = RouteOptions.builder()
.applyDefaultNavigationOptions()
.applyLanguageAndVoiceUnitOptions(requireContext())
.coordinatesList(listOf(originPoint,destination))
// provide the bearing for the origin of the request to ensure
// that the returned route faces in the direction of the current user movement
.profile(DirectionsCriteria.PROFILE_DRIVING)
.waypointTargetsList(waypoints)
.language("en")
### Expected behavior
Route map should be loaded with waypoints
### Actual behavior
Route map is not coming, route line is also not there. Navigation icon is moving at some other location
### Is this a one-time issue or a repeatable issue?
repeatable
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 issue with mapbox-android-sdk:mapbox-android-sdk:9.6.1 using RouteOptions.builder(), coordinatesList, waypointTargetsList, and the supplied points. Inspect how the route request and returned route map handle waypoints. Done means the route map and route line load correctly and the navigation icon follows the expected route with waypoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100