Indeed, long press the waypoint you want to continue at to start navigation from there 🙂 This can be done in the route overview screen or a when the navigation is already running.

Thanks for sharing the crash information. Could you by any chance share your iPhone / iOS version and a screenshot of the app permissions?

I had the same problem, the blue viapoint (hand) had a question remark all the time and I just saw the km's but without "km" after the digit. I your picture is "mi" presented but I didn't see "km" today?

sometimes I sas also the end flag (left on top) in the middle of a route point and didn't have the next turning point that you can see below the flag.

@Steve-Autera

I have been using an iPad Pro and an older 6th Gen 9”. iPad for many years with MRA RoutePlanner.
In my experience I have found that using the “Place Waypoint Button” option seems to be more efficient than manually adding the Waypoints.
Even with this implemented, you can still manually place a waypoint on the Route between 2 other waypoints by just clicking on the Route Line.
Also it is advisable to zoom in the full extent when placing any waypoints.

@Corjan-Meijerink top!

@Steve-Lynch This something we might need to tweak a bit 😉

See this conversation too: https://forum.myrouteapp.com/topic/3225/navigating-a-track-goes-directly-to-destination

Happy to hear that! 🙂 We look forward to all the requests!

Badminton is cool too! Did that for some years but squash is my true passion

@Gary-Weidenhamer Thanks for sharing! This is an issue we are aware of but rather hard to tackle as the data we receive is incorrect. That said, we will continuously aim at improving this! 🙂

@John-De-Jong

BD5464F1-BB67-441D-BD87-41E233CF4EFE.jpeg

3D2B0F92-C747-41A2-816F-0A54CFB1B24C.jpeg

2B0591BB-C007-4A26-990B-14AC02FF6B3D.jpeg

@Corjan-Meijerink said in 3.2.7-149 Still Crashing:

@Tim-Thompson I do see some reports showing some improvements but yes, we will definitely keep working on this!

You probably did already do so, but could you share your device information? 🙂

My phone details...

Pixel 5a
Android Version 13
Build Number TP1A.221105.002

@Corjan-Meijerink Brill. Thank you for the update. Looking forward to the next changes being released. Excellent work.

@Vince-Hyde said in Crash:

@Corjan-Meijerink mine still crashes 50% of the time on the first few tests, one phone did the update and crashed first time i re opened the app attempted to open a route again and it closed and put a message image below. i cleared the cache and it opens a route on a second attempt on my other phone i did not auto update so I uninstalled the old cleared the cache and installed the new version and it closed on all first attempts and the opens the route

Idem pour moi, Samsung S21 FE

@Robineke Interesting issue, thanks for sharing! Will investigate 🙂

@Corjan-Meijerink Great, thank you .

@Erik-van-Dijk-0 Na het bewerken via de routebewerker moet je de route even opnieuw openen in de app.

@Corjan-Meijerink said in 3.2.6-147 Still Crashes:

Could you by any chance detect a pattern in the crashes?

We have been able to resolve the Android crash issue affecting some users not being able to load a route at all. The last thing we want is the app being less stable for others 😉

These crashes are quite complex to debug so any information at all can help! 🙂 Device / Android version too!

No not really. All I can tell you so far is that it consistently does it when I click here...

38cb194f-9cbf-469f-976e-9a0605623892-image.png

... sometimes when I click here...

97a66a43-19b3-484f-a66a-0b79ba7ff20f-image.png

I've also noticed it randomly crash a few occasions while perusing various menus.

My phone details...

Pixel 5a
Android Version 13
Build Number TP1A.221105.002
MyRoute-app Mobile Version 3.2.6-147