You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating an app where user can configure locations for routes and I use mapbox to draw optimized routes based on the user's selected locations.
So initially when the app launched, I have some dummy locations which I optimize for shorted route using MapboxOptimizationAPI. Then after I show that route on map.
This works fine. But I have strange problem. After initially route has been decided, if I want to add new location to existing route and then re-ask Mapbox to provide route in this case I am getting "Refused to schedule onboard router request as pending request with id 1 has already finished" error and always timeout.
However, if i do not initiate route request to mapbox initially(when app launched), and in this case if I add /update/delete locations and re-ask mapbox to provide me route then it works fine.
I am not sure what is happening as both request are just same only one extra location.
I have attached my Activity file for your reference.
Please suggest me what I am doing wrong.
I have already opened ticket on Mapbox Support Center(https://support.mapbox.com/hc/en-us/requests/160654), but i haven't received any response on it.
I have a subscription plan purchased and still not received any response since last 13 days so i am creating an issue on Github.
Hi ,
I am creating an app where user can configure locations for routes and I use mapbox to draw optimized routes based on the user's selected locations.
So initially when the app launched, I have some dummy locations which I optimize for shorted route using MapboxOptimizationAPI. Then after I show that route on map.
This works fine. But I have strange problem. After initially route has been decided, if I want to add new location to existing route and then re-ask Mapbox to provide route in this case I am getting "Refused to schedule onboard router request as pending request with id 1 has already finished" error and always timeout.
However, if i do not initiate route request to mapbox initially(when app launched), and in this case if I add /update/delete locations and re-ask mapbox to provide me route then it works fine.
I am not sure what is happening as both request are just same only one extra location.
Initial Request: https://api.mapbox.com/directions/v5/mapbox/driving/72.5088127,23.0277154;72.528799,23.038374;72.563378,23.042054;72.56928,23.04024;72.571362,23.022505;72.601948,23.003785?access_token=****Ad_Q&geometries=polyline6&alternatives=true&overview=full&steps=true&layers=0%3B%3B%3B%3B%3B&continue_straight=true&annotations=congestion_numeric%2Cmaxspeed%2Cclosure%2Cspeed%2Cduration%2Cdistance&language=en&roundabout_exits=true&voice_instructions=true&banner_i...
After adding new location Request: https://api.mapbox.com/directions/v5/mapbox/driving/72.5088127,23.0277154;72.528799,23.038374;72.563378,23.042054;72.56928,23.04024;72.571362,23.022505;72.601948,23.003785;72.5590226,23.0762103?access_token=****Ad_Q&geometries=polyline6&alternatives=true&overview=full&steps=true&layers=%3B%3B%3B%3B%3B%3B&continue_straight=true&annotations=congestion_numeric%2Cmaxspeed%2Cclosure%2Cspeed%2Cduration%2Cdistance&language=en&roundabout_exits=true&voice_instru...
I have attached my Activity file for your reference.
Please suggest me what I am doing wrong.
I have already opened ticket on Mapbox Support Center(https://support.mapbox.com/hc/en-us/requests/160654), but i haven't received any response on it.
I have a subscription plan purchased and still not received any response since last 13 days so i am creating an issue on Github.
Android API:
Mapbox Navigation SDK version: : 3.2.0-rc.1
Steps to trigger behavior
Description has all details for triggering
RoutePreviewActivity.txt
Expected behavior
Actual behavior
Getting Error: Refused to schedule onboard router request as pending request with id 1 has already finished
The text was updated successfully, but these errors were encountered: