IOS: App crashes 2-3 times a day (v5.1/5.2)

[Peter Zehentreiter]

@RetiredWingMan Are you using MRA to navigate online or offline?

Could it be that newer Android devices running Android 16 or Android 17 are more vulnerable?

[Adrian Avram]

@RetiredWingMan said:

Most of my ride are 5 to 6 hours. Never a problem with NN.

I've even done an 18-hour drive, stopping only for gas, without any issues whatsoever!
I guess it comes down to either the hardware or the app settings for those who are experiencing problems.

[AWDC LAO]

@Aiello-antonino

From 07:00 AM till 17:30 PM - 270 km with lot of waypoints.
4 days ( +/ 1100 km ) in France when t° during the day between 35-43° C
With an iPhone 12 Max Pro and also a Carpe Iter v4c ( android is not 100% foor connection with 5G, 4G, 3G but with personal hotspot via Iphone 12 it was better )

[Aiello antonino]

Did you have the tracklog active?

[Peter Zehentreiter]

@Aiello-antonino It’s not down to the tracklogs

I also had problems without tracklogs enabled

[Aiello antonino]

Oh ok…for example, I always have the tracklog active and I have had problems every day I travel…

[RetiredWingMan]

@Peter-Zehentreiter. I use both off line and on line. Depends on where I'm traveling. No idea if newer devices have more issues. I always purchase older new or used phones.

[RetiredWingMan]

@Aiello-antonino. I generally always have a tracking running. The only time I've had issues is running a round trip which i think was a Track. It's very touchy about missing a turn. Also seems like if it gets confused and decides to send you back to the start of the track there is no way to get NN to continue in the Track.

[Aiello antonino]

I've always used routes and an active tracklog, and I've had problems. I was trying to make some hypotheses to understand what the conditions are that cause the app to crash. It seems to work well with offline navigation. I don't know, but let's hope they find a solution.