i hav since 6 days the same problem. The Version of my “Kurviger Pro” !!! app is 1.14.23.
With WLAN already is okay but with mobile is “No route found” when i want to start this route with download. Start a simple route with searching a place bring also the message “No route found”.
I love this app 5 years but now is this huge crap. Please help me and the other biker.
Thanks and bye bye
I use trhe app on 2 mobilephones. One is a Samsung SM-G900F and the other is a Xiaomi Mi 9SE. The problem is on both phones the same und every mobilphone has a other provider.
I have the same problem “route not found” with 2.2.23, I don’t know since when it doesn’t work since I haven’t used it for days.
I have no antivirus or firewall or adblocks enabled.
It didn’t work wlan, mobile or brouter with airplane mode, I updated brouter and neither.
After searching and testing I saw that it was a route that I had generated from the web and exported as “.kurviger” which had been left open but being away from my current location I had not noticed.
I found out by going to “tools> info”
I deleted this route and everything works again, both from calculating route online and with brouter.
This happened to me with 2.2.23 but possibly with 1.14 the same thing happens, I’m sure @devemux86 will be able to review and fix it. Thanks!
I would say that the solution to avoid this problem would be as simple as if the program has an open route and you want to calculate another one it will warn you that “there is already an open route” instead of “route not found”
@Kai_Hirschbach , look this, I think I discovered the problem
It didn’t work wlan, mobile or brouter with airplane mode, I updated brouter and neither.
After searching and testing I saw that it was a route that I had generated from the web and exported as “.kurviger” which had been left open but being away from my current location I had not noticed.
I found out by going to “tools> info”
I deleted this route and everything works again, both from calculating route online and with brouter.
This happened to me with 2.2.23 but possibly with 1.14 the same thing happens, I’m sure @devemux86 will be able to review and fix it. Thanks!