MRA 5.0 - 422 Route / RoutesTrack Stop No / Navigate

[Hubert Thoring]

Hello dear successful MRA team,

The app is just great, I just noticed the last little point.

Test - Route / RoutesTrack:

If I start a navigation from A to B in the app, which I select as B via "Search for a favorite or a gas station" ... Then it starts directly via navigation.

Noticed: on the route

Now I deliberately stop the route, then picture 1 is not offered to me. The route is stopped directly without the "No / Navigate" option.

Wish:

• It would be wonderful if you still had the option.

Noticed: at the routeTrack navigation

• Now I deliberately stop the route track, then I will be offered picture 1. The "No / Navigate" option can be selected.

Selection: No

• then stop the route track ... okay

Selection: Navigation

- Error navigation no longer works

- there was a calculation that does not yield a result, the process cannot be stopped ... s. Picture 2

• it's like an endless loop / crash

Solution:

• App must be terminated / aborted with wipe (iPhone).

Restart:

The route appears with the menu picture 1

• The option "No / Navigate" can be selected.

• The same error is repeated when you press navigation again

Picture 1

Picture 2

[Hubert Thoring]

I could make a video if desired because the description seems incomprehensible.

VG

[Jörgen]

Ich verstehe nur Bahnhof! - I don't understand a word!

[Jörgen]

Can you please explain step by step how you get to the error?

[Hubert Thoring]

Hey everyone,

Here is the video about the MRA RouteTrack, and its problems when restarting the navigation...

Link zum Video

[Jörgen]

Ok, now I understand.
A restart is not possible. I tried on my iPhone and saw the same problem.
On Android, it is working.

[Jörgen]

Sorry correction!
I just updated Android.
With V 422 it is the same on Android. No restart possible.

[Con Hennekens]

@Hubert-Thoring, a simple "resume navigation after a stopped route does not work" would have sufficed. It saves a lot of pictures and a video. This problem is already being discussed with devs.

[Hubert Thoring]

@Con-Hennekens :

[Corjan Meijerink]

This is now fixed, thanks for reporting