08-14-2017
15:19
- last edited on
09-12-2017
14:20
by
KateFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


08-14-2017
15:19
- last edited on
09-12-2017
14:20
by
KateFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
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:
- What is your Fitbit app version (account > help)?
- What version of iOS are you on?
- Have you tried what worked for @ReneRobles and continue to hit the try again button?
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-24-2017 12:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-24-2017 12:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
08-24-2017 15:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-24-2017 15:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I talked with online chat tech support a few nights ago, spent over 30 minutes trying various things - uninstalling, reinstalling, resetting the Flex 2 back to factory... Nothing worked. The tech support lady said that the tech people are aware of the issue and they're working on it and it will be fixed in the next update and that was the end of the chat. I'm really hoping it won't take too long before that comes out.
08-24-2017 16:14 - edited 08-24-2017 16:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


08-24-2017 16:14 - edited 08-24-2017 16:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Everyone -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.
Actively managing your weight? Find accountability buddies on the Manage Weight board

08-24-2017 17:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-24-2017 17:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-24-2017 19:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-24-2017 19:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I returned mine and exchanged it for a new one. It works just fine. I tried for 3 days to get the first one to work. Who has time for that??
08-25-2017 04:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 04:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
me too. so annoyed and frustrated 😕
she couldnt even give an approximate ETA 😐
I ended the chat because I knew I wasn't going to get a replacement. And told me to try using it on my computer for the meantime but.... it doesn't work either .___.

08-25-2017 04:32 - edited 08-25-2017 04:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 04:32 - edited 08-25-2017 04:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I tried to exchange it at the store but was told that I had to go through the online support 😞 so I can't even exchange it to see if it would work ~ sigh.
So disappointed...

08-25-2017 05:10
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 05:10
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
@ErickFitbitI am having the same error. To answer your questions:
1) I'm on Fitbit 2.39 (691)
2) iOS 10.3.3
3) yes I tried a few times and still wont work
08-25-2017 05:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 05:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 08:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 08:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I have a screenshot of this message but not sure where to send it?

08-25-2017 17:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 17:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Brand new Flex2 and can't pair or update because of this code. Come on man, what's the fix? Thanks-

08-25-2017 17:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 17:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Sent from my iPhone

08-25-2017 19:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 19:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks.
Sent from my iPhone

08-25-2017 20:56
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-25-2017 20:56
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Received following message when trying to update FitBit Blaze
"The operation couldn't be completed. (FBBluetoothErrorDomain Error 18.)
what is latest status? It's been almost 2 weeks. Also notifying Fitbit is not holding charge beyond a day anymore.
Have had it for awhile with no issues until latest update

08-26-2017 10:36
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-26-2017 10:36
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello,
I have got a Fitbit today and I'm having the same error. Not sure if I needed to report this separately. Is the issue almost resolved?
Amy

08-26-2017 11:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-26-2017 11:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Same issue here with a BRAND NEW device. We are very disappointed. Did not hold charge either.
Will return if not resolved!!!!

08-26-2017 14:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-26-2017 14:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I bought Flex 2 yesterday and couldn't get it updated. I kept pushing 'try again' relentlessly and it was finally updated!!! Thank you 😊

08-26-2017 14:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-26-2017 14:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I was on the phone with a Fitbit tech today for over an hour trying to get my Flex 2 synced and get the update loaded. Finally he said it sounded like it was defective and told me to return it. My husband is going to try to go with the Charge 2 to see how that works.
My original Fitbit was a workhorse and I wore it every day for 2 years until the battery died and we were unable to find another one.

08-26-2017 20:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-26-2017 20:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
For me it seemed to be just a Apple product and windows 10 issue.
I tried it on a Samsung device and it successfully updated and now it works.... previous issue of not seeing the sleep stats also works now... 😕

08-27-2017 03:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-27-2017 03:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Ive got this problem too - is the fix out yet?

