08-30-2019 15:55
08-30-2019 15:55
I get this notification on my phone each time I'm not right next to it. I get all the notifications on my watch like normal. It's syncing with each other, so why does this notification pop up? And how do I make it go away?
08-30-2019 19:13
08-30-2019 19:13
Hi @Kathariu What phone are you using? Is it on the Supported Devices List?
Try uninstalling the app and then reinstall it and log back in
Helen | Western Australia
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
08-31-2019 00:41
08-31-2019 00:41
I have a Samsung s8
Tried uninstalling and installing and logging back in.. And still getting the same message 🤬
08-31-2019 03:17
08-31-2019 03:17
I have the same problem. It all started whith the latest update.
08-31-2019 04:49
08-31-2019 04:49
Same issue here on a Samsung S8
It started with the new app version... moreover it seems the app is draining a lot of battery 😞
08-31-2019 06:56
08-31-2019 06:56
I also use an S8 but have had no problems with my Versa. I really dont know what else to suggeat except contact Support (link in my signature)
Helen | Western Australia
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
08-31-2019 11:53
08-31-2019 11:53
I'll tack on another "Me too". Only appears when Versa and my phone (Pixel 3, which is on the supported devices list) aren't nearby -- for instance, if I leave the watch on the charger in the other room overnight.
09-01-2019 00:15
09-01-2019 00:15
I managed to solve the issue (for now)
* unlinked the Versa
* complete de-install & re-install the app
* multiple reboots of the Smartphone
* relink the Versa
09-02-2019 11:09
09-02-2019 11:09
And one day later, the problem is back... No sync betwen Veras and the phone, without a phone reboot.
Very disappointing
09-05-2019 07:45
09-05-2019 07:45
I've had the same issue as well as constant sync issues starting shortly after installing the new version of the app. I constantly get the message in the subject or I'll get sync errors (No device found) which results in me having to put the Fitbit in the cradle (it's a Flex) and reset it, or reset my phone, or turn off bluetooth and re-enable, or force stop the Fitbit app, or some combination of all of the above.
Yes, my device is on the supported list as I'm sure just about everybody elses is that is responding with the same issue.
It seems that Fitbit released the new version of the app and changed not only the interface (which I like) but somehow changed the sync process, which seemed to be working just fine in the past. It seems they did not follow the old adage "If it ain't broke, don't fix it."
Fitbit first needs to acknowledge this and to offer a fix. This has been a disappointing couple of weeks when it comes to my device, and it sounds like I'm one of many.
09-13-2019 04:40
09-13-2019 04:40
I am also having this same problem. I have a Samsung Galaxy S9+.
09-13-2019 05:13
09-13-2019 05:13
Whenever I get this pop-up in the app, whether I press Cancel or OK, that is the point where my connection becomes unreliable and the Sync Service notification completely disappears.
For some reason it seems to be a completely unnecessary prompt, because when I ignore it my watch keeps synchronizing like a dream. But as soon as I choose an option the problems begin. 🤷🏻:male_sign:
09-14-2019 17:03
09-14-2019 17:03
Same here with S10! No fix yet?
09-14-2019 19:48
09-14-2019 19:48
Same problem with galaxy s9+. Also having issues with bike ride. Phone app shows a dot and no map tracking. Logging into website shows full ride map. Just started with new version. I had ALOT of problems a year ago, but last 9 months was fine. How can they change things that were working.
09-15-2019 00:00
09-15-2019 00:00
Which version of the app is everyone using?
I'm using version 3.5 (which claims to be upto date) and haven't experienced the issue described. I'm wondering if there is a newer version floating around that some of us haven't got yet.
09-15-2019 05:38
09-15-2019 05:38
09-24-2019 08:06 - edited 09-24-2019 08:07
09-24-2019 08:06 - edited 09-24-2019 08:07
I am using version 3.6.1 (according to google play's app info, this version is new on 9/19/19), but I am still have this same problem so this update did not fix it.