App Freezes When Skipping Waypoints

Bug Report – App Freezes When Skipping Waypoints (iPhone)

When I’m navigating a route and try to use the “Skip Waypoint” function to remove a waypoint, the app freezes and becomes unresponsive.

I have to clear the app’s cache and restart it to get it working again.

The “Skip Waypoint” function does not work properly.

Thanks for letting us know. I can reproduce this issue, could you please provide more information?

Does this happen with every route? Only with a certain number of skipped wps?

Can you share a screenshot of your debug information (Kurviger app, settings, scroll down).

Hi,

Thank you for your response.

The issue occurs with every route during actual trips, regardless of its length or the number of waypoints.

Whenever I try to skip a waypoint after navigating for some time and having already passed several waypoints, the app freezes. This has happened consistently on my trips.

Interestingly, I have just carried out a test using a very short route of only a few metres with several waypoints, and the Skip Waypoint function worked correctly.

This makes me wonder whether the issue might be related to the duration of active navigation or the number of waypoints already passed. I’m not sure if this information helps narrow down the cause, but I thought it might be relevant.

As a workaround, I have to stop navigation, edit the route, manually delete the waypoint, and then restart navigation. Although this works, it is not particularly practical, especially while travelling.

Having the Skip Waypoint feature working reliably would be fantastic, as it would make navigation much more convenient and seamless.

Hello ,

to understand this, what does long mean ( I rode 22000 km with it ) and how many waypoints per 50 100 km ???

or even better, since you’re an experienced user, just post the route right here.

VfL (VzG)

My routes are usually between 100 and 200 km long, with a few shaping points and via points.

For example, if I try to skip a waypoint after about an hour of navigation, the app gets stuck in an endless loading loop and never completes the operation.

I’m attaching just one example of a route where this happened when I tried to skip a waypoint. And this isn’t even one of my more complex routes.

Do you have a recalculation on and if yes, was there internet connection available.

Does it happen in simulation mode too?

It would be helpful if you could share a route where it happens, so someone could try to reproduce it:

That raises the suspicion that, with all those avoidances, Kurviger can’t find a route.
Even though it’s been mentioned 1000 times here in the forum… try removing the avoidances for main roads and highways, then it will work. Then select extra curvy or curvy and you’ll easily get those tiny backroads preferred.

Do you still have the debug info for us, please? You can find it in the Settings if you scroll all the way down.

Hi,

I’m attaching a photo, but I’m not sure if it’s what you’re looking for.

To clarify, I made a typo, I can’t reproduce this issue. Sorry for that.

@jgouvsa it would be great if you could have a look a this. Any information would be helpful to find the actual culprit. As it is, we are not sure why the app behaves this way for you.

Maybe the issue was fixed with version 3.6.7? But I would have expected that there would have been more complaints if there was a serious issue like that?

I’ve actually been trying to reproduce the issue, but so far I haven’t been able to.

I’ll keep a close eye on it, and as soon as the issue occurs again, I’ll provide all the necessary information to help identify the root cause.

Hopefully, it has been resolved in version 3.6.7!