Maybe for bugfix useable:
Ok, I can start that route in simulation mode (both with GPS on or off).
So I think the developers themself must help …
Debug-Informationen:
Device: asus - P027 - Android: 7.0 - WebView: 119.0.6045.193
@Max.outdoor has a Carpe Iter device. I think it is special and cannot be compared with a standard mobile phine. As far as I know the manufacturer must do special programming for integration. I would suggest he asks the manufacturer by link he provided, if there are known issues by other users.
I am sorry to hear that there is an issue. Just to clarify, did you maybe load an old .kurviger file? Could you try to delete the current route and just plan a very short route and try to navigate that? Just to make sure there are no other issues involved.
I actually thought they fixed this with the Android 11 update (I might be wrong though). But we haven’t had any recent complaints, so I thought this was fixed.
Can’t start the navigation. Error: Could not parse Kurviger Models
(Debug information, this helps us helping you, you can remove this if you don’t want to share this data, it should not contain any personal or sensitive information)
Device: HMD Global - Nokia XR21 - Android: 13 - WebView: 125.0.6422.54
App-Version: 3.3.2 - 2938
Screen: 432 x 960 px - 2.5dppx
Interesting, thanks for letting us know. Can you check my answer above to see if this might help?
If not, could you try to provide some more information?
I delete the file and tried to make a short route but that didn’t work.
Too bad that there are no answers to clear the issue.
Hoping that that te problem can be solved soon.
Otherwise kurviger has no value for us.
All three of us have the same problem.
I am sorry that you are having an issue, but so far we don’t know how to reproduce the issue. This is not a known issue.
So you are a group of 3 people and you 3 all have the same issue and can’t resolve it?
It’s interesting that this seems to hit all 3 of you. And a reinstall of the app and a short clean route does not work either?
Can you share the .kurviger file you used or anything else that could help to clear up the situation? I tried the link above, but I am able to start the navigation for this route.
… probably the other 2 too.
I don’t think so - also the screenshots don’t match a tablet
Device: HMD Global - Nokia XR21 - Android: 13 - WebView: 125.0.6422.54
We ar all having the same problem, can not start your requested route. We are navigating with smartphones. Except one us is using the old kurviger app an can load from the web version to the old app and this works fine.
Could it be a language thing, encoding, copy, paste from somewhere into kurviger? Above the two routes are “nordic”, with special characters. Strange we can use it. Just an idea.
And a reinstall of the app and a short clean route does not work either?
We tried, deleted all files, new kurviger app, restart phone, but same problem.
Another idea … account could have an issue.
When you clear the route, are you able to start at least the follow mode?
Second test: logout (to use it as free account).
Can navigation be started without route (follow mode), if success - follow mode with very simple route?
To focus the issue, please try to reduce the route to its segments, only 2 points:
S1. only start and waypoint 1
S2. only waypoint 1 + 2
S3. only waypoint 2 + 3
…
S14. only waypoint 13 + 14
S15. only waypoint 14 and destination
Can you start any segments? Which ones?
Ok, this is a very interesting issue. I can reproduce the issue. This only occurs in special situations. It appears one of our calculations fail, if you are too close to the poles (apparently the north cape is enough for this). I will send you a hotfix for this in the next half hour. We will fix this properly in our next release (but I would like to avoid releasing a hasty BETA today, but we will release one probably next week).