[iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction
-
I deleted the app till we know more!
-
But its only in build 6183? If I use an older version the problem doesn’t happen?
I have no routes in SA so far, because all my routes are in MC.
And what does MC un-safe mode mean?
This is really an unfortunate move from Suunto to their not-S3F-owners…
-
@jthomi Yes, Is only build 6183.
The scenario that @Brad_Olwin tell us in my case is not reproduced.
But yes, perhaps we could avoid build 6183 till things are clarified.
-
How do you install older versions?
-
@johan6504 TestFlight > previous builds
-
in the TestFlight app, enter in the Suunto App details, choose option Previous Builds and there you could choose the version to install, the previous one is 1.0.1 (6160)
-
Exactly the thing I will do now until we know more. Really time now for Suunto to clarify things up about Movesount AND / OR SuuntoApp.
@aldnet said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:
@jthomi Yes, Is only build 6183.
The scenario that @Brad_Olwin tell us in my case is not reproduced.
But yes, perhaps we could avoid build 6183 till things are clarified.
-
That is really bad … communication and even more sensivity towards the users
-
@shrek3k that’s why we are beta testers, sometimes such things happens. Imagine such with official app, suunto support wouldn’t be happy…
-
@slash I absolutely agree, but isn’t that the reason why (even) beta testers quite often receive information about the changes, so that they are aware of all the major changes … otherwise I still agree, that whoever does betas should not be to afraid to be surprised
-
@shrek3k well for me was quite unpleasant surprise that app can kill watch sync with cable. Now I will read changelog more carefully before update
-
@slash said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:
@shrek3k well for me was quite unpleasant surprise that app can kill watch sync with cable. Now I will read changelog more carefully before update
I am much more motivated to read now, too … “fortunately” the Android change log is much shorter 🤨 -
@shrek3k said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:
“fortunately” the Android change log is much shorter 🤨
-
[just to make it really clear: I am purely envious about the longer change-log for iOS, but definitely not about the bug … although it would be nice to be able to directly send routes to my watch ]
-
About using buld 8163, doesn’t use routes but still with problems to sync via movescount, check that suunto app is not in background
I have tested now and both apps works correctly, but closing SA before open MC
-
@slash @aldnet @jthomi I have reverted back to the last SA build and will continue to use that until this sorts itself out. I ended up having to reset the watch twice and could not get (6183) to work properly with either MC app or the cable. Part of my problem may have been routes from both SA and MC in my watch. Lots of time wasted, which I don’t want to do again. I did sign up for a beta so I am not angry but there are more issues here than just the routes. In addition, route sync does not work properly from SA as no elevation profile information is transferred to the watch. I wish that some of the outstanding bugs in the SA app could be fixed before new features are implemented.
-
@luís-pinto Ambit3 & Traverse will be supported soon
-
@jouko-from-suunto Good news because many users have that watches and can integrate this forum.
I fear however, resources that people are accustomed in Movs app will not be implemented in SA, such personalization of watch and workout planner.
-
@shrek3k
“fortunately” the Android change log is much shorter"the Build release note is usually huge, but there is 500 char limit in Google Play so stripped to minimal. Have to be careful when checking what has to be there and what can be left out
-
@jouko-from-suunto said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:
@shrek3k
“fortunately” the Android change log is much shorter"the Build release note is usually huge, but there is 500 char limit in Google Play so stripped to minimal. Have to be careful when checking what has to be there and what can be left out
Un fortunately, the Android change log is short
It is quite sad to read : bug fixes and improvements, …, nothing else.
Some of us are beta testers, and others “simple” users.
And tracking bugs, not even knowing what is known to be fixed, is very difficult.We have discussed somewhere about a part of the forum for beta test discussions, like a “closed” group.
Isn’t it the time for re thinking of it.