help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Still sync issue with blaze and iOS 10.2

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎01-31-2017 05:29

‎01-31-2017 05:29

I have not been able to sync for 3 days. App is updated firmware is updated. I have rebooted blaze, turn Bluetooth off and on and even unpaired the device. The app shows a low battery level even though I have charged it, because it has not synced since Saturday.

Best Answer
3 REPLIES 3

‎01-31-2017 06:57

‎01-31-2017 06:57

I have same issue. But mine tries to sync over and over. Also time is wrong

Best Answer
0 Votes

‎01-31-2017 13:06

In response to pamb166

‎01-31-2017 13:06

Yes my time is about 6 minutes off my phones time.

Best Answer
0 Votes

‎01-31-2017 13:38

In response to Willybit

‎01-31-2017 13:38

I jumped on the phone with Customer Support and they helped me trouble shoot the problem and now it works.  Mine was not syncing and I could not get update to load.  I shut off bluetooth, logged out of the fitbit in account settings.  Turned off phone..then turned it back on, logged in, turned on bluetooth and it could a while but finaly was able to sync and install upgrade...all working fine.  She told me that there is an issue with the latest IPhone upgrade and this is the fix.  Good luck

 

Best Answer
0 Votes