24/7 tracking not synced in SA anymore

Spree

This is almost invariably an app cache issue.

If uninstalling and reinstalling didn’t do the trick (surprising, though), try to manually delete the cache of the app, then log in again.

A Former User

@spree
tx. before reinstalling I did it. on the watch too.

Ander Lehena

@walker said in 24/7 tracking not synced in SA anymore:

morning all,
suddenly w/o any reason since 5 days or so 24/7 tracking, i.e steps/calories/etc. are not synced w/ SA anymore.
moves are ok.
on the watch tracking is ok.
I’ve already tried to reinstall SA.
thoughts? thanks.

p.s. I’ve read a user had a similar problem w/ a S9 if I’m not wrong

I have this problem in my S7

A Former User

@walker
as extrema ratio during lunch break I’ve tried a factory reset… still no data synced.
the only thing recently changed has been the SA update to 2.7.0 [iOS]

I’ve opened a support ticket w/ Suunto, let’s see what happens now.

lexterm77

@walker

Same here,

Resources and sleep tracking no longer sync. Routers and activities do. I restarted the watch, no help.

I also have S9P, S5 and S9B paired to the same phone, no problems there.

I have noticed that my local maps downloads have been interrupted frequently lately and when they finally started working again, this issue with resources and sleep syncing popped up.

A Former User

@lexterm77 said in 24/7 tracking not synced in SA anymore:

I have noticed that my local maps downloads have been interrupted frequently lately and when they finally started working again, this issue with resources and sleep syncing popped up.

me too!

taujin

@walker having similar issue as well. manually cleared the cache but doesn’t help either

lexterm77

@taujin

I reset the watch completely from factory. Issue remains.

I did not install any apps on new watch, just kept it plain vanilla including all the settings,
Still does not sync resources or sleep.
Routes and activity are working,

Egika

@lexterm77 I had the same with some 2.7.0 beta versions.
Beta 2.8.0 seems to resolve it

lexterm77

@egika said in 24/7 tracking not synced in SA anymore:

@lexterm77 I had the same with some 2.7.0 beta versions.
Beta 2.8.0 seems to resolve it

No betas, all current pub releases. It’s been a week now.

Brad_Olwin

@lexterm77 contact support

Brad_Olwin

@lexterm77 I used my S7 today and will track resources and will sleep tonight with the watch and let you know what happens. I switch watches often on the iPhone. I am running alpha SA software, one jump ahead of the betas that are on the forum here. That is one difference. My S7 is running production firmware.

Ander Lehena

@brad_olwin Is that production firmware one that has not yet been released to other users?

Egika

@ander-lehena Production firmware means this is the firmware everyone else is using, so the public version.

Ander Lehena

@egika I was hoping that there would be firmware in testing🥲

lexterm77

@brad_olwin

I will take my spare iPhone and pair it with a spare non titanium S7 that I have on same SA account, eliminate as much as possible before contacting support.

Edit: My other iPhone and my other S7 device (public release all sw) still does not sync resources or sleep data.

Brad_Olwin

@ander-lehena said in 24/7 tracking not synced in SA anymore:

@brad_olwin Is that production firmware one that has not yet been released to other users?

No, it is the standard production firmware all you have.

Brad_Olwin

@walker @lexterm77 This is not working for me or for some other testers either. A bug report is filed with Suunto. This should be a fix to SA as the watch seems fine. I would use the most recent beta apps as that will have a fix before an App Store release. To clarify is this restricted to iOS or is it occurring on Android as well?

Egika

@brad_olwin as I have the same I have gone back through the iOS betas and found that 2.7.0 (9162) seems to be the last working version

lexterm77

@brad_olwin said in 24/7 tracking not synced in SA anymore:

before an App Store release. To clarify is this restricted to iOS or is it occurring on Android as well?

Issue is fixed with new public SA release on iOS.