-
@Djanbgo said in Syncing problems Ambit3 with iPhone11:
Hi All,
I have made a new try after long while without using the phone. It now works fine to sync my iPhone 11 with my ambit. I was able to sync my 20 works. Finally !
Note : I am on IOS13.6.1
Regards,What changed? App?
-
@André-Faria I have not done anything special, just unpaired, paired and I was surprised to see it synced. I have seen lately an apps update done … So …
-
Apps are being rolled out in BETA with various fixes. I am going to “shout out” here when needed to inform the public
-
It suddenly started working for me also (latest iOS). Without pair/unpair procedure. Nice
!! -
iOS update
CHANGES 1.71.0
Ask user to update the watch with SuuntoLink if too old firmware is detected
Ask user to remove pairing from phone settings if system level pairing detected while removal needed
Fix for emptying sync cache watch disconnected or unpaired
Fix for data packets lost on sync level
Removed unnecessary unsubscription & subscription to watch resources when connecting and re-connecting watchCHANGES 1.72.0
Connectivity fix for Spartan and S series devices, fixes a bug created in 1.71.0
Keep Bluetooth connection on during workout sync for Ambit 3 and Traverse even if the device goes to sleep mode
Please keep me posted!
-
1.71.0 and 1.72.0 only in apple store no ? In TestFlight ( Beta Program ) 1.7.0 (8418 ) no more upgrade since 29 days
-
Dimitrios says that, This is for production rolling out
-
That’s great neeeeeews !!
-
@Djanbgo I have also managed to sync my iPhone 11 using latest iOS 14.1 with the 1.72.0 release. I haven’t yet tried it with an activity but getting it to sync was good news.
-
Uploaded an activity directly from Ambit 3V to iPhone 14.1 without any problems using 1.72.0. Many thanks!!!
-
It seems that sync is working now.
Tested on Ambit3 Run, iPhone 11 (iOS 14.2), Suunto App 1.72.0
Geia sou Dimitri!
-
@GeoSo Hello Giorgo!
-
I’m impressed, syncing via the app works exactly as expected now.
Thank you very much to everyone that worked on communicating this issue and solving it. It would have been easy to just walk away from the problem.
