Waypoints feature is unreliable unless app is in the foreground about organicmaps HOT 5 OPEN

Thanks for feedback, need to be tested on Android

from organicmaps.

Thanks for the details, indeed there is an issue. Someone can try to reproduce it with a debug build (or in simulator), maybe by adding some additional logs where necessary, to understand why the waypoint is not automatically removed.

Likely we need to handle background activity more reliably in iOS. There are no background directions yet, for example.

from organicmaps.

On the UI, there should be a way to interact when one arrives at an intermediate waypoint, just like when one arriving at a destination. When arriving at the navigation, one will stop the navigation, or otherwise, when one moves away from the destination, OM will still continue to guide the user back towards the destination.

from organicmaps.

@hoizan let's create a separate issue for the UI/UX.

Does it also reproduce on Android? I assume that OM on iOS doesn't get location updates in the background now (see #6940 ), maybe except for cases when a recent track is enabled in settings. @fizwidget can you please confirm whether the issue reproduces or does not reproduce with the recent track enabled?

from organicmaps.

Hi @biodranik, I’ve been able to reproduce it with recent tracks enabled. I can see the blue dots passing in very close proximity to the waypoint, yet OM still wants me to backtrack to it. Here’s an example:

Perhaps it’s worth mentioning that I usually don’t linger at waypoints - instead, I walk straight through them. So if the code expects the user to remain stationary at the waypoint for a while, I guess that’d explain the problem I’m having. EDIT: Actually that can’t be it, because waking straight through waypoints works fine when the app is in the foreground.

from organicmaps.