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

Brad_Olwin

@aldnet as you can see from my final note below, even when I force quit the app it synced before I could get the cable attached and synced. I cannot afford to lose my sync with MC and until there are more tests done I am unwilling to use SA.

Frankly, this is what I was concerned about a couple weeks ago when the route notification first showed up. We have no idea where Suunto is going and basic bugs in the app have yet to be fixed. (route elevation profile among others). I realize this is beta but…if the beta compromises what I use the hardware for it is a real problem.

aldnet

@fleshymutant In my case, no, is not working, in fact the windows app disabled some options after manipulating routes in suunto app.

Brad_Olwin

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

And I don’t know why is so complicated, but yes, elevation bug is still present, in the notes of the version is indicated.

I am not talking about the elevation bug in the app for reporting elevation, at least the watch knows what is correct. When you sync a route with SA the breadcrumb syncs (where you are going) but the elevation profile does not so you have no elevation profile for the route…I use the elevation profile more than the breadcrumb track. I reported this bug when route syncing first appeared, it is still not fixed and is a basic functionality of routes implemented on the Spartan.

SlaSh

@fleshymutant create route via suunto app sync it to the watch and your sync with Mc and cable is gone only watch reset helped to recover it…

aldnet

@brad_olwin ok, I see, but today I realize it, when you create a route in Suunto App, I didn’t see the elevation detail in the summary of the route in the app, so I guess is for that in the watch elevation is not there too.

I suppose is the way Suunto App (before sports tracker) create routes

Brad_Olwin

Very, very bad… iOS 11.3 and Mac for MC. Spartan 2.0.40

This morning I synced a route with the newest SA app (header here). Saw the notice and synced move with SA app, no syncing to MC either with cable or app.

Reset watch, erased all routes in SA app, resync watch to MC and route from MC as well as training syncs…all good.

Test short move. Sync to SA app (no routes in app and no route syncing from app)

NO Syncing to MC either cable or app

I am resetting the watch AGAIN.

I will delete the SA app

My experience: Syncing a route SA, resetting the watch, erase all routes, if you sync with SA you LOSE MC syncing, period.

johan6504

I deleted the app till we know more!

jthomi

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…

aldnet

@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.

johan6504

How do you install older versions?

SlaSh

@johan6504 TestFlight > previous builds

aldnet

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)

jthomi

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.

Shrek3k

That is really bad … communication and even more sensivity towards the users

SlaSh

@shrek3k that’s why we are beta testers, sometimes such things happens. Imagine such with official app, suunto support wouldn’t be happy…

Shrek3k

@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

SlaSh

@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

Shrek3k

@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 🤨

suzzlo

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

“fortunately” the Android change log is much shorter 🤨

Shrek3k

[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 ]