Comment 5 for bug 1809915

Hi Costales,

I managed to fix this bug, but when I build the app by myself, it never picks the GPS correctly and I'm somewhere 1000 km away from my location. It's because your specific release script replaces API tokens for the online services? Or does it perform any more changes to the code? I sometimes see comments like "/** TESTING BEGIN **/" and corresponding ending tag". I didn't get into the code much yet.

Anyway, solution is to remove wrong options header in "WebAPI.js" on lines 62 and 151 and replace it with just required feature like this: '{"avoid_features":"tollways"}'.

And for this "feature" there seem to be a limitation of max. 300km long road on the server side. But I'm not sure, if its general limitation or it relates to the used API tokens in devel code. Generally API returns error with message and specific code, maybe uNav could show the message instead of just "Not found" when looking for the road. Similar to the warning when user is planning more than 1000km long trip.

Thanks for the great app.

Pavel