The improvements in recent updates, specifically concerning track-based navigation, have tempted me to reinstall MRA Navigation again after a long time. In theory, this is exactly what I was hoping for when MRA Next was first announced way back when and for the most part, it works quite nicely. Good stuff! I've tested it over the weekend on a route I know quite well, where I made a couple "mistakes" on purpose to see how the system would handle it. The basics went quite well, but I did encounter a few issues. The first issue I encountered is that the route I had planned (using the web planner, on the TomTom map) had already changed when I viewed it in the app, because of a ferry crossing (which we know HERE doesn't handle correctly, it tried to send me around adding 30 minutes and 20 kms to my trip; yes, I know there's a work-around, no, I'm not going to use it). So, sadly, it seems I'm still not able to trust that my planned route will not be touched when using it for navigation, even with track navigation, which is one of the main reasons I don't want to use route-based navigation for planned routes (simple A-B is fine, of course, but that's not what I use MRA products for). The second issue was that I (on purpose) put a Via-point on one road and then (again, on purpose) used a different road. The good thing is that the system (with recalculations enabled) handled my deviation quite nicely: recalculation was quick and suggested a reasonable alternative route. Obviously, it tried to send me back to the missed Via-point (as expected). What I did not expect, was that I had to skip multiple waypoints to get rid of that. As I did this while driving (yes, I know I shouldn't have), I didn't notice which point(s) I actually needed to skip manually (automatically skipping waypoints is enabled in the app, not sure if it affects track-based navigation?). I got the impression that it may have been asking me to skip all points (including shaping points) from the start of the route and not just the via-point I missed, but it could also be that it somehow didn't correctly register that I wanted to skip the via-point and just kept asking me about the same point multiple times. A third, completely separate, issue I've noticed on a few occasions, is that I get a notification that the app has crashed after I've used CarPlay, but I haven't used MRA itself). I'm using the latest iOS version (just updated to 18.2, but also noticed it with 18.1) and the latest beta (haven't tried it with the official release yet). I've had this before as well (with way older versions). I've mostly been using the betas, so it could be a beta-only/TestFlight issue.

TestFlight says 375, Correct?

Massive update and very promising. Thank you

@Corjan-Meijerink Thank you, I will test it on some longer distance, when possible.

SilverFox bar buttons correctly zoom again

@white-mouse-on-the-motorbike is zeker verbeterd! Maar beetje afhankelijk per type telefoon nog op dit moment. Door de daling vd temperatuur neemt het verbruik sowieso ook al af!

Ben benieuwd om dit aan komende zomer uit te testen betreft de hitte! Mijn telefoon werd tijdens het motorrijden in Frankrijk afgelopen zomer vaak onleesbaar tijdens het navigeren hahaha

Ook via android playstore beschikbaar. Net geüpdatet!

Na het verkrijgen van de nieuwe Beta update gisteren weer een poging gewaagd. In eerste instantie het MRA nog steeds moejte om met AA te verbinden. Na een paar maal gestiopt te zijn en zowel de app als AA opnieuw gestart te hebben kreeg ik een stabiele verbinding en bleef MRA via AA normaal functioneren. Het lijkt er dus op dat het probleem over is.

@Corjan-Meijerink : Everything perfect under iOS I am thrilled everything goes without problems for the motorcycle and the Mobile phone .... I have read V4.3.2 (346) is already there great performance.!!! Alles perfekt unter iOS ich bin begeistert alles geht ohne Probleme fürs Motorrad und dem Handy …. Habs gelesen V4.3.2 (346) ist auch schon da tolle Leistung.!!! [image: 1729090621912-img_8738.jpeg]

@michaelblaas-nu We are working on it! If you want to revert to the public release, unsubscribe as tester temporarily as explained here: https://forum.myrouteapp.com/post/17830 You can then always join as beta tester again as explained in the the same post

@white-mouse-on-the-motorbike dankje, we gaan het onderzoeken. Zou je een support ticket kunnen aanmaken met daarin de logs van je app? Deze krijg je door het versienummer onderaan je profiel pagina (waar alle instellingen staan) lang in te drukken. Pak ik hem daar op

@Corjan-Meijerink 336 update What’s new/changed?

@richtea999 Fixed in the release (I've heard)

@Stanisław Oh definitely! We will solve this. Logs can be obtained by long pressing the version number shown at the bottom of your profile / account page (where all the settings are).

@Corjan-Meijerink Made a round tour in the Eifel yesterday of approx 350km using MRA with AppleCarplay in my Z4. No issues (so the stability improved) and changes needed due to roadblocks/maintenance could be made with succes. Referring to that, will it be possible in the near future to see the next way-point on AppleCarplay? (like we had before) This makes is possible to skip waypoints, to avoid a roadblock for example, on the screen without using your iPhone. Thanks.

@Jan-Weerheim Geweldig! Heel fijn om te lezen. We hebben veel tijd gestoken in het intuïtief maken. Mooi als dat lukt

@Hubert-Thoring nice to hear that!

@Corjan-Meijerink : There would still be something to adjust before the published... at least from my point of view something that could be even better so that the user learns to love it before he does it badly. Test der neuen v4.2.0 (320) Small things, but they should also go clean without compromise.

@Tom-Johann And yet we have an even better version, 4.1.3 (311)!