Thanks for report. Since 1.5.22 are asserts again reported (there used to be reported approx year ago). It is often hint for following troubles. In your case the first assert is about validity of route edge and it is invalid. Is it one particular country?
We released 1.5.22 as stable version so beta testing topic is "deprecated". Important is that @mdx know about this problem, it sounds critical so I think he gave it big priority
We probably fixed "assertion failed (line:56 in src/ItineraryProxy.cpp)" problem - it may not crash application. Can I ask you for routing points where you get "assertion failed (line:115 in src/RouteEdge.cpp)"?
When it crushes all the routing points are cleared.
But on Tuesday I had the same problem again on a different route. This time I had 2 devices with me - one with 1.4.24 version and the other with 1.5.22. (I have reloaded the route and attached the screenshots)
I was navigating using the 1.4.24 and I had the 1.5.22 in my pocket.
Results 1.4.24 finished with no problems 1.5.22 crushed ( as it was in my pocket I dont know which routing point but looking at the logs I think it was just after waypoint 10 which is lat=51.92575449, lon=-1.72567507)
The fact is that when that happens the application "crashes" or closes down. Then it needs to be restarted, load the route, work out which waypoints to clear and start the navigation.
You did say that is important it gets fixed. I am just looking for some time-scales as I would like to start using the latest version as well.