RoadManager for osmdroid error

Let’s try to provide a complete answer to this quite frequent question.

Basically, when you get the “straight line”, it means that the RoadManager got an error.

So, first of all, in your code, you should check the result of getRoad, this way:

if (road.mStatus != Road.STATUS_OK){
  //handle error... warn the user, etc. 
}

Now, where this error is coming from?
=> You must search in the logcat. You should find the full url that has been sent, and probably a stacktrace about the error.

I strongly recommend that you copy/paste this full url in a browser , and check the result.

Here are the typical errors, by decreasing probability:

1) You didnt’ read carefully the “Important note” at the beginning of the Tutorial_0, and you are trying to do a Network call in the main thread, with an SDK >= 3.0.
=> Read this “Important note”.

2) You asked for a route that is not possible (really not possible, or because of weird positions, or because of setting unsupported options).
=> This is easy to check by copy/pasting the full url in a web browser, and looking at the answer.

3) Your device has no network connectivity.

4) The routing service changed its API (this happened, more than once…).
=> Could be checked by copy/pasting the full url in a browser.
In this case, raise an Issue in OSMBonusPack project, so that we can take it into account ASAP.

5) The routing service is down.
=> Easy to check by copy/pasting the full url in a browser.

Leave a Comment