05-23-2016 12:01 - edited 10-06-2016 10:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-23-2016 12:01 - edited 10-06-2016 10:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
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.
07-24-2016 19:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-24-2016 19:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-24-2016 19:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-24-2016 19:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Sent from my iPhone

07-25-2016 05:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
07-25-2016 05:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello everyone and welcome to the Fitbit Forums! I'd like to start by saying thank you for the continue reports of the "exercise not synced" error. Our team is still working on a fix for this issue, @DerrickS will post in this thread once he receive mores updates.
Please do not uninstall the Fitbit App. There is the potential of losing any unsynced data if you uninstall the App. I recommend logging activities on Fitbit.com until a fix is available.
Thanks for your patience and understanding while we work out this issue.

07-25-2016 06:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 06:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Walker12,
I believe the cutoff to be after 60 minutes and their server application will reject it depending on server load.
I must have lucked out during my 7am CST sync from the FitBit iOS application to the FitBit online-dashboard, because it was successful. A full day late.

07-25-2016 06:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 06:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
First: good to hear from FitBit that they are aware of this problem and that they work on a solution.
However, it really is hard for me to believe that this problem has any priority for fitbit because it has been known for months ...

07-25-2016 06:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 06:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
07-25-2016 06:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 06:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
TheFitFireman,
Thank you for the sound advice!!! Im going to add it to my above response.
Additionally, after many, many, many attempts. I have been successful in my brute-force attempt to sync.
I have managed to sync ALL activities that would not previously sync.
Try and try and keep trying you all. IT WILL WORK EVENTUALLY.
To the FitBit moderators, my friendly suggestion is to FORCE this up the ladder. This is a priority to those of us who share + utilize GPX+CSV data.
Thank you,

07-25-2016 07:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 07:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
We appreciate that you contacted us via Twitter, our team has passed your case to our T2 Team and we're currently working on it. We checked with our engineering team and they have confirmed that this is a known issue and they're further investigating and resolving this issue.
We appreciate your patience with this matter. Please let us know if we can assist you further.

07-25-2016 07:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 07:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Walker12,
Keep trying my man. It will sync eventually. Cummulative time spent attempting to sync: ~2 hours.
It will sync eventually.
My suggestions are to pick a time of day where you think there will be the fewest amount of people using FitBit services - super late night or super early morning.
BIG THANKS to @SunsetRunner for recommending the BRUTE FORCE option. By repeatedly attempting to sync iOS data to online dashboard, I was successful. This took many, many, many tries. Probably upward of 75 total attempts and 2hr of time.
KEEP TRYING EVERYONE.

07-25-2016 07:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
07-25-2016 07:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 07:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 07:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@SunsetRunner
This is my first experience with this matter.
Previously, all of my tracked activities would immediately upload without issue. I was not experiencing any problems until my activities went over 40-50 minutes. After that, I had the "not synced" error.
Have you noticed activities of a minute duration failing to sync? Or did you experience this error/bug with all activities?

07-25-2016 07:58
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
07-25-2016 07:58
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
My MobileRun activities are always longer than 1hour so I cannot help to prove your idea. In my experience MobileRun never sync at the first attemp. At first the iOS app need to sync data from the fitbit (HR, steps, Kcal) and usually it tooks 3\4 sync attempts, then I start the Brute Force and as you experienced it tooks many many tries.

07-25-2016 08:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 08:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Patricia
Sent from my iPhone

07-25-2016 08:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 08:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@picasso66 @SunsetRunner
Picasso66, The brute-force method is many many attempts; wiki "proof by exhaustion".
https://en.wikipedia.org/wiki/Proof_by_exhaustion
https://en.wikipedia.org/wiki/Brute_force
Simply trying, and trying, and trying, and trying, and trying.
Keep trying 🙂 Never quit!

07-25-2016 08:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
07-25-2016 08:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@picasso66 it's easy: when iOS app says not synced you try to resync, wait and if it fail you keep trying as long as it works. The worst thing is that you may need a lot of attempts.

07-25-2016 08:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 08:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Patricia
Sent from my iPhone

07-25-2016 15:41
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 15:41
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@picasso66@SunsetRunner
Did a 32 minute cycle. It synced without my intervention.
This function works but only within a specifc set of parameters on specific devices.
FitBit moderators could probably fill us in on the rest. Personally, I would either 1.) keep it under 60minutes tracked activity OR 2.) brute-force sync.
Proof of concept:

07-25-2016 21:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
07-25-2016 21:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 23:42
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-25-2016 23:42
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-26-2016 13:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
07-26-2016 13:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I had several hikes and walks that I tracked with the app (I only have a zip fitbit) that were not synced for the last several months, same issue everyone else is describing, but for me the last update seems to have deleted them entirely. I know what days they were as I mapped them manually on runkeeper and saved the info the fitbit app would show me but would not sync. They're all just gone now, not in the app and not on the site. I did not uninstall the app, I just ran the update from the app store.
I hate logging things manually on the site as it overwrites the step data from my zip, so this experience has be questioning owning a fitbit at all at this point if I can't reliably use it.

