Issue with 4.0.0 185

Vince Hyde

although my beta version looked fine I decided to install the public version so I left the test and downloaded the new public version. I have logged in and it has all my map folders but if I try to navigate it asks me to subscribe.

after this, I re-joined the beta test and re-downloaded the beta and it asks the same. to subscribe?

Corjan Meijerink

@Vince-Hyde are you logged in with the right account? Otherwise it’s best to contact support about this matter. Check your account page on mra for that email to see if you indeed have the correct licenses (https://www.myrouteapp.com/account)

Vince Hyde

@Corjan-Meijerink I only have one account, I have lifetime gold on both and it shows all my maps so I do not understand why it thinks I need to subscribe.

Corjan Meijerink

@Vince-Hyde but do you also have Navigation? Gold is another product.

Otherwise best to contact support!

Vince Hyde

@Corjan-Meijerink Yes that's how I became a beta tester, I thought

Vince Hyde

@Corjan-Meijerink If I open a route it shows everything but the nav is in grey if I press the navigation it puts a message!

then if i click on trial i get

and if i press to open shop i see

Vince Hyde

@Vince-Hyde if i try to look at the account page all i see is the bit at the bottom with no sign out bit and the back arrow doesn't work and I have to close the app

Corjan Meijerink

The issue has been fixed! Please see this announcement: https://forum.myrouteapp.com/topic/4598/update-4-0-1

alan cookson

I am experiencing the same problems i am lifetime gold and lifetime navigation but am getting exactly the same screens as Vince is there a problem with logging in?

TerWalle

@Corjan-Meijerink for me the problem has not been solved. I cannot log in anymore. However My routes are still in the app

Con Hennekens

@alan-cookson and @TerWalle, did you guys install the update? It was released just 2 hours ago...

Hans Mester

@Con-Hennekens It's not yet in the Play Store (Almere, Netherlands)

Corjan Meijerink

Correct! Update (4.0.1 - 188) is being processed. This should solve the issue.

Con Hennekens

@Hans-Mester, it is now...