12-27-2017 15:01 - edited 01-11-2018 15:45
12-27-2017 15:01 - edited 01-11-2018 15:45
Update: 1/11/2018: Hi everyone, I receive confirmation that the Error 24/Error 8 issue is now resolved. Thanks very much for your reports and of course your patience. If you are still seeing this error message, please let me know.
Hi Everyone - I've merged a few posts. We are currently investing reports of Surge users unable to set up their tracker on iOS, seeing: Error 24, followed by Error Domain Error 8.
At this time, the best workaround we see is having users set up on the Windows 10 app or an Android. They are then able to sync normally to an iOS device. I know that's not ideal and will continue to update this thread as I hear more. Thanks for your reports and patience.
Actively managing your weight? Find accountability buddies on the Manage Weight board
Answered! Go to the Best Answer.
01-04-2018 05:01
01-04-2018 05:01
01-04-2018 05:32
01-04-2018 05:32
The USB cable didn't work for me, but the dongle did, so I suggest you make the additional effort to try that.
01-04-2018 05:57
01-04-2018 05:57
I got this message from Fitbit in Facebook, it didn’t work for me but it might for some of you? I don’t have a computer so can’t try the dongle and Windows 10 fix, I’ve also had another email from Fitbit support just saying they are still trying to fix the problem.
01-04-2018 08:37
01-04-2018 08:37
It works! They have fixed it. Just updated on my iPhone 👍👍thanks Fitbit.
01-04-2018 08:46
01-04-2018 08:46
Just bought a surge for my father. Getting the error 24, called Fitbit support and they said they are working (last week). So now he has a watch that can’t even display the time of day. This watch and company is not worth the box the watch came in.
01-04-2018 08:48
01-04-2018 08:48
Try again, mine just worked on a iPhone 6 - Been trying since Christmas Day and it finally works.
01-04-2018 09:01
01-04-2018 09:01
You must be lucky, mines still the same 😱
01-04-2018 09:34
01-04-2018 09:34
Now I get the error 8. I guess that’s a step in the right direction. I called Fitbit support again to request an email to tell me when their update is complete and they flat out told me no.
01-04-2018 09:50
01-04-2018 09:50
01-04-2018 11:25
01-04-2018 11:25
Still not working for me either! And sadly I got excited to come home from work and try!!! 😞
01-04-2018 12:44
01-04-2018 12:44
Can you please confirm when the error will be resolved as I can't connect my new surge either via the Fitbit App.
@KateFitbit wrote:
Hi Everyone - I've merged a few posts. We are currently investing reports of Surge users unable to set up their tracker on iOS, seeing: Error 24, followed by Error Domain Error 8.
At this time, the best workaround we see is having users set up on the Windows 10 app or an Android. They are then able to sync normally to an iOS device. I know that's not ideal and will continue to update this thread as I hear more. Thanks for your reports and patience.
01-05-2018 04:01
01-05-2018 04:01
01-05-2018 04:31
01-05-2018 04:31
01-05-2018 12:37
01-05-2018 12:37
01-05-2018 15:37
01-05-2018 15:37
01-05-2018 15:41
01-05-2018 15:41
Still no joy with registering and syncing my new surge - what is happening?!?!
01-06-2018 04:23
01-06-2018 04:23
I only have a Mac and an iPhone! When will there be an update on this?
01-06-2018 06:24
01-06-2018 06:24
I finally managed to pair mine by downloading the app to my daughter’s kindle, using the option to load an upgrade for the surge (which came up on the homepage) and then setting up the new surge. I’ve since opened the app on my iPhone 5S and Mac and it’s working!
01-06-2018 06:33
01-06-2018 06:33
Awsome @naomijoy
ALAN | VAN,B.C. Canada Community Council Member
Versa, Charge, Charge HR, Ionic, Ace, Aria 2 scale, Flyer headphones - iOS
Click here Fitbit help for more solutions
01-06-2018 06:34
01-06-2018 06:34
Cannot believe that this is the best Fitbit can offer? Maybe us Apple users should just bin our fitbits and get Apple Watches instead? Dreadful customer service. Assuming you are infect going to fix this please advise as soon as resolved