05-23-2016 12:01 - edited 10-06-2016 10:43
05-23-2016 12:01 - edited 10-06-2016 10:43
Fitbit Update 9/19/16
This issue where users experience a red "(not synced)" error next to their exercise logs on the iOS App has been resolved with the release of iOS App version 2.27. Click here to update your App if you haven't already.
Thanks you for everybody's patience while we worked this one out!
Fitbit Update 5/23
There is currently a bug where some iOS users see a red "(not synced)" error next to some of their exercise logs. Our team is aware and currently working on fixing this bug. Apologies for any inconvenience that this creates.
Please do not uninstall/reinstall the Fitbit App, uninstalling/reinstalling the Fitbit App could cause data loss. If possible, I would also recommend logging activities on Fitbit.com until a fix is available.
Answered! Go to the Best Answer.
09-12-2016 12:45
09-12-2016 12:45
09-12-2016 12:45
09-12-2016 12:45
09-12-2016 13:04
09-12-2016 13:04
Didn't get their money's worth out of me! I have had multiple Fitbit Flex, Charge, and Charge HR replaced under warranty. They have to be losing money on me by now!!
09-12-2016 21:00
09-12-2016 21:00
8/29 - Walk - 1:33:30 (5610 seconds) - GPS/HR/steps sync FAIL
8/31 - Walk - 1:22:50 (4970 seconds) - GPS/HR/steps sync SUCCESS
9/5 - Walk - 1:29:01 (5341 seconds) - GPS/HR/steps sync SUCCESS
9/6 - Walk - 1:30:01 (5401 seconds) - GPS/HR/steps sync SUCCESS
9/8 - Walk - 1:32:02 (5523 seconds) - GPS/HR/steps sync SUCCESS
09-14-2016 06:52
09-14-2016 06:52
Keep trying to sync your activities, everyone.
Repeat, repeat, repeat. It will sync eventually.
09-14-2016 08:04
09-14-2016 08:04
09-14-2016 08:52
09-14-2016 08:52
Besides, the point is that we shouldn't have to "keep trying." The fitbit and app should work like it's supposed to...
09-14-2016 08:56
09-14-2016 08:56
I lost two runs last week in my troubleshooting but let one sit this week and it eventually did sync. I agree, something as simple this should not be so challenging. I cannot blame it on connectivity; I had good Wireless and at another time very good WiFi signals.
I have seen similarities. It seems that when you cross the 1 1/2 hour threshold something happens. I don't know if this is something Fitbit could change on server settings or give us a timeout setting in the app. It looks like there are just too many datapoints to sync normally.
09-15-2016 22:08
09-15-2016 22:08
09-16-2016 11:05 - edited 09-16-2016 11:06
09-16-2016 11:05 - edited 09-16-2016 11:06
has been fixed with the newest update. i have synced my 99 min run.
09-16-2016 13:12
09-16-2016 13:12
09-16-2016 16:16
09-16-2016 16:16
I just updated 2.27. All unsynced from July to last weekend have updated.
Thank you
09-16-2016 17:09
09-16-2016 17:09
Me too! Finally! Thanks, fitbit.
09-16-2016 19:07
09-16-2016 19:07
09-17-2016 02:30
09-17-2016 02:30
My hikes from June 8 have finally synced
09-17-2016 14:05
09-17-2016 14:05
09-17-2016 14:06
09-17-2016 14:06
09-17-2016 22:14
09-17-2016 22:14
Hi, DerrickFitbit, it seems installing Apple ios 10.01 eradicates the bug. I'm not sure why I'm telling you this instead of vice versa. I get Apple and Fitbit aren't pals, but with a billion iPhones sold, maybe the folks there might want to factor that into their priority task tree.
Just sayin'.
09-18-2016 08:51
09-18-2016 08:51
09-18-2016 09:09
09-18-2016 09:09