08-14-2017
15:19
- last edited on
09-12-2017
14:20
by
KateFitbit
08-14-2017
15:19
- last edited on
09-12-2017
14:20
by
KateFitbit
Fitbit Update 9/12/2017: This issue was resolved in the new app update version 2.40 released yesterday. If you are still experiencing this issue, please update your app. Thanks for your patience!
Fitbit Update 8/24/2017: Thanks again for reporting this issue, at this time we have all the information needed and our team is still reviewing. I'll update this thread once we learn more. Your patience is truly appreciated.
Fitbit Update 08/14/2017: Everyone -- Several iOS users have reported receiving the FBBluetoothErrorDomain error 18 when attempting to update their trackers on the latest version of the Fitbit app for iOS, version 2.39. Our team is currently aware of this issue and working on a fix for this. I appreciate you taking the time to report this issue.
As @Rich_Laue asked here, can someone please share a screenshot of the error message as well as letting me know the following details:
I will pass this information along to our Product Specialist who will provide me with an update and I will make sure to convey that to you all. Thanks again for your reports. More information coming soon!
08-27-2017 04:46
08-27-2017 04:46
08-27-2017 08:29
08-27-2017 08:29
I am also having this problem with a Fitbit Blaze with an iPhone. We have tried to uninstall/reinstall the app, restarting bluetooth, stopping/starting the fitbit device, selecting the 'try again' button on the error message 20-30 times without good results. I am hoping this issue is resolved soon as it appears that it was reported almost 2 weeks ago. That is a long time for a bug which causes a device as expensive as a Fitbit Blaze to be in-operational. We are pretty upset about this and really hoping for a resolution.
08-27-2017 09:36
08-27-2017 09:36
I'm wondering.... is this just an IOS problem? Or are there problems with the other platforms? I returned my Flex 2 yesterday after an hour with a tech who couldn't help me. My husband just ordered me a Charge 2. I'm hoping I won't have the same problem.
08-28-2017 04:26
08-28-2017 04:26
Has this issue been resolved? Mine is still coming up when I try to update 😞
08-28-2017 06:43
08-28-2017 06:43
08-28-2017 06:49
08-28-2017 06:49
Nope. Just tried to synch my Fitbit with phone (iPhone 7) and same error still comes up. Going on over 2 weeks now. What's the point of having Fitbit if it doesn't synch?! So frustrated!
08-28-2017 07:13
08-28-2017 07:13
08-28-2017 07:17
08-28-2017 07:17
Have had the Blaze for over a year now and it worked great. Only the latest update back in middle of august created all these issues. Sounds like its major glitch on their end and affecting all the Fitbit's. They have to fix it or the whole Fitbit company will collapse
08-28-2017 12:39
08-28-2017 12:39
Fitbit Blaze will not update. Tried with PC and with App - neither work. Advise?
08-28-2017 12:58
08-28-2017 12:58
08-28-2017 15:29 - edited 08-28-2017 16:14
08-28-2017 15:29 - edited 08-28-2017 16:14
I received the same Bluetooth error, ErrorDomain 8.
Hitting Try Again repeatedly (20 times) did not solve the problem.
I am using a Fitbit Charge 2
My Fitbit App is version 2.39 (691)
My IOS version is 9.3.2 (13F69)
My iPhone is a 6 Plus
Update: Solved using Brooke's method.
Just saw Brooke's post, tried re-pairing my tracker with the App and now it is updating.
(Went to iPhone Bluetooth screen and selected "Forget Device" for tracker, then went to FitBit App and selected "Remove Tracker from App", shut down iPhone, restarted iPhone, restarted App, put tracker very close to iPhone and followed the usual prompts to pair the tracker to the iPhone/App. Update completed successfully after about 5 minutes. Now Tracker is correctly Sync'ing data with iPhone App.)
08-28-2017 16:01
08-28-2017 16:01
08-28-2017 16:28
08-28-2017 16:28
For @AnnGK and others. Removing the tracker from your Fitbit account or app should not be needed. This only affects the tracker and your Fitbit account, forcing you to set up the tracker and possibly losing any unsynced data.
Telling the phone's bluetooth to forget, then forcing a sync should be enough. It is the sync that sets the bond up between the tracker and the phone.
08-28-2017 17:03
08-28-2017 17:03
08-28-2017 17:07
08-28-2017 17:07
08-28-2017 17:15
08-28-2017 17:15
My Flex 2 arrived today and I am also getting this error (FBBluetoothError Domain error 18)
08-28-2017 17:18
08-28-2017 17:18
Rich, that worked!! Hallelujah!!
told my iPhone 7 to "forget this device" on phone. Went to try and remove tracker on app but couldn't find where to do it. Option came up to "pair up device" so I figured I would try it. And it worked!!
thank goodness for this community of replies because Fitbit isn't getting back to anyone!
08-28-2017 18:05
08-28-2017 18:05
have tried to update new Alta on iPhone 6s at least 30 times - continue to get FBBluetoothErrorDomain error 18.
Fitbit App Version: 2.39 (691)
iOS Version: 10.3.3
08-28-2017 18:28
08-28-2017 18:28
Hi all - I just got mine to work! I tried all the solutions posted here but none worked for me on my iOS. I used my husband's phone to update my tracker instead, he has an HTC 10 but I would suspect any non-iOS would help.
I turned off my iPhones Bluetooth then shut down my Fitbit app.
On the HTC 10 I installed the Fitbit app then signed into my account and added my new Flex 2. It paired up and installed the update just fine.
Then I unpaired the HTC10 from my tracker and signed out of the app.
Back to to my iPhone - turned Bluetooth back on, and signed into the Fitbit app. It paired up and synced my tracker just fine.
So it appears once the update can be installed successfully using a non-iOS phone, the iPhone will be able to pair up and sync OK.
I hope this can help someone else!
08-28-2017 18:44
08-28-2017 18:44