This object is in archive!
Route planner fails with index out of bounds exception.
Closed
Nav backend: brouter.
A straight line is drawn, then error is shown in toast. this happens on a few tries for same sourceand target point, then just draws the line without the toast. looks like this happens if distance is too great, but 26km, really?
This isnt the first time it happens to me, but first when i hav time to report it.
Seems, like this nice feature introduced annoying issues. Previous method of composing tracks was very simplistic and one did not expect much, but at least it did not fail so often.
Files:
Screenshot_2018...
The same problem 
Good day Bartek,
sorry for a complications! Is it possible for you to write me start point coordinates, end point coordinates, routing engine (GraphHopper, ...) and type of transportation you use? For me, is important to simulate exactly same problem on own device. Thank you!
Good day Bartek,
sorry for a complications! Is it possible for you to write me start point coordinates, end point coordinates, routing engine (GraphHopper, ...) and type of transportation you use? For me, is important to simulate exactly same problem on own device. Thank you!
Hi Menion,
Will do once i'm back home and try to reproduce this issue (and then some). Saturday the earliest.
Still, btw, I consider Locus to be the best there is :)
Thanks!
On May 2, 2018 9:25:02 AM GMT+02:00, Locus Map <locus.map@asamm.com> wrote:
Hi Menion,
Will do once i'm back home and try to reproduce this issue (and then some). Saturday the earliest.
Still, btw, I consider Locus to be the best there is :)
Thanks!
On May 2, 2018 9:25:02 AM GMT+02:00, Locus Map <locus.map@asamm.com> wrote:
Hi,
So the issue is gone, perhaps because in the meantime I've downloaded new brouter data for this area (Poland). I was using the Locus profiles at the time if that matters.
I'll keep watch for those out of bounds errors and let you know it this happens again.
And also for force closes, which I had some too. Which is another matter entirely, since if a force close happens BEFORE I leave the route planner in mid planning, that work will not be saved. So - restoring previous planner session only works if planner was left properly, not by a force close.
Hi,
So the issue is gone, perhaps because in the meantime I've downloaded new brouter data for this area (Poland). I was using the Locus profiles at the time if that matters.
I'll keep watch for those out of bounds errors and let you know it this happens again.
And also for force closes, which I had some too. Which is another matter entirely, since if a force close happens BEFORE I leave the route planner in mid planning, that work will not be saved. So - restoring previous planner session only works if planner was left properly, not by a force close.
Good day Bartek,
thanks for the information. If this happens in future again (hope not), please let me know. In case of full app crash, best is to report such issues together with the created log by this method: http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log
About lost plan in case of the crash: well, it is important not to have any crashes at first :).
Menion
Good day Bartek,
thanks for the information. If this happens in future again (hope not), please let me know. In case of full app crash, best is to report such issues together with the created log by this method: http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log
About lost plan in case of the crash: well, it is important not to have any crashes at first :).
Menion
Replies have been locked on this page!