[iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction

Jouko Tyni

@aldnet Had to verify this a bit and this comes from the dev team now: if you have routes created with earlier versions of the app the watch do not go to unsafe mode. Only until you create new route with this version or edit old one the watch will be put to Movescount unsafe mode.

You may be also interested to learn this detail: If you do push the watch to MC-unsafe mode that and for any reason regret, you must reset the watch in order to recover.

aldnet

@jouko-from-suunto thanks, so I will remove the route, and check what happen with a activity I will perform this afternoon.

And also if it put me in MC-unsafe I will reset as you suggest

Dimitrios Kanellopoulos

To be honest I am surprised about this decision and very interested to see how we can still manage both apps sync

aldnet

@dimitrios-kanellopoulos without syncing routes

@aldnet said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:

@dimitrios-kanellopoulos without syncing routes

i do my routes-handling via movescount only, then it should not be a problem at all.
as watch settings can just be synced with movescount (app) or suuntolink (pc & cable) i still use mc for all this stuff.
SA just for playing around and testing the app - i just sync my excerises there too.

aldnet

@asdf123 yes

Till all the routes from Movescount could be visible to Suunto App for me the first resource was Movescount

Even with the fact that I cannot convert a activity to a route in Suunto App as we could do with MC.

SlaSh

Just did a lunch walk and my activity do not sync with MC, I am getting frustrated…

suzzlo

so…

If you Create and edit routes in MC and just view en SA, will watch sync in both systems?

johan6504

This is a little confusing…I am not ready to give up MC sine this is the way for synk with Strava. Can I keep testing the app or should I remove it? I do all route planing in MC, never in the app…

Dimitrios Kanellopoulos

@johan6504 From what I understand if you use MC for routes you are fine.

SlaSh

@dimitrios-kanellopoulos problem is that I have deleted routes which were created by suunto app from watch and suunto app and my sync to MC now is affected even without any routes

johan6504

@dimitrios-kanellopoulos Ok, I’ll stay away from the app routes until we know.

Dimitrios Kanellopoulos

@slash said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:

@dimitrios-kanellopoulos problem is that I have deleted routes which were created by suunto app from watch and suunto app and my sync to MC now is affected even without any routes

No idea about that.

To be honest I dont like this change and I am a bit on rage here. Must go for a run

johan6504

@dimitrios-kanellopoulos That might turn out to be a good run, good luck!

aldnet

@dimitrios-kanellopoulos @SlaSh that was my scenario too. I understand that the fact to delete, put the watch in Movescount-unsafe for what says @Jouko-from-Suunto

Resetting the phone for second time in less than 24 hours, yesterday for problems with gps and battery consume.

aldnet

@suzzlo yes, in fact routes from MC are not displayed in SA.

If we wan to keep using both systems, don’t use route feature in Suunto App.

Dimitrios Kanellopoulos

@aldnet said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:

@suzzlo yes, in fact routes from MC are not displayed in SA.

If we wan to keep using both systems, don’t use route feature in Suunto App.

he does and cant at he is on Android

aldnet

@dimitrios-kanellopoulos what do you mean, behaviour is different in Android?

@aldnet said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:

@dimitrios-kanellopoulos what do you mean, behaviour is different in Android?

yes, as there is not route sync at all so far
see also https://forum.suunto.com/topic/867/android-3-33-0
–> Route sync not available yet

Jouko Tyni

@aldnet I have to admit that I’ve not tested this myself. If this 6183 is not working for you there is also possibility to downgrade the app in TestFlight app to the previous beta version. Anyway to me this seems like a good show case what will happen in production if we have users who would like to use also MC for any reason (Strava connection to be the most obvious one atm). Let’s see if there is anything we can change based on what we should learn from this.