10-03-2019 13:45
10-03-2019 13:45
After upgrading my iPhone XR to IOS 13 the Charge 2 would not sync with the iPhone. I removed the Charge 2 and attempted to reinstall it. When I tried to do "set up" I got the message to turn on Bluetooth.
Bluetooth was on but the Charge 2 would not connect. I attempted to do some of the suggestions on this forum (like removing all Bluetooth devices on the iPhone and restarting it and the Charge 2) to no avail.
Charge 2 firmware version is 22.58.00 iPhone IOS is at 13.1.2
Answered! Go to the Best Answer.
10-03-2019 18:41
10-03-2019 18:41
This is outstanding @Oalaska!
Im happy your back up and running....Happy Stepping! Could you please mark my instructions as the best answer in my post with the instructions on the suggestion fix.....it really helps others who are seeking answers to issues similar to yours. I would appreciate it. Thank you. 😃
10-03-2019 16:52
10-03-2019 16:52
Hello @Oalaska
I understand your having syncing issues. I see you have turned the Bluetooth off then back on again Let’s try this. Log out of your FitBit App then force shut the app by swiping up. Make sure your Bluetooth is indeed on then shut down your phone completely and wait about 1 minute then turn your phone back on again. Once your phone is fully loaded log back into your Fitbit app as you normally would with your email and Password. Try to sync the app now.
😃 please let me know if this gives you an answer to your syncing issue
10-03-2019 17:15
10-03-2019 17:15
10-03-2019 17:28
10-03-2019 17:28
Hello again @Oalaska I think the best course of action now would be to just reinstall the Fitbit App. (you will not lose your data doing this) Just uninstall the app, then completely shut down your device and wait about 1 minute then turn your device back on. Once it fully loads head to the App Store and reinstall the Fitbit app and simply login to the Fitbit app as you normally do by inputting your email address and password. Try to see if your Fitbit sync now. Pay special attention to the app hopefully asking permissions to pair...of course say always when asked.
Please let me know if this solves the Bluetooth issue
10-03-2019 18:37
10-03-2019 18:37
10-03-2019 18:41
10-03-2019 18:41
This is outstanding @Oalaska!
Im happy your back up and running....Happy Stepping! Could you please mark my instructions as the best answer in my post with the instructions on the suggestion fix.....it really helps others who are seeking answers to issues similar to yours. I would appreciate it. Thank you. 😃
10-09-2019 21:29 - edited 10-10-2019 04:09
10-09-2019 21:29 - edited 10-10-2019 04:09
Running Fitbit Firmware 22.58 on my Charge 2. After updating my iPad to iOS 13.1.2 on 10/8, my Fitbit would only sync if I restartEd it every time. I also only got simplified sleep stats that night. Tried your advice, MegaBite, and logged, out, reinstalled, logged back in, etc. My iPad can no longer find my device at all. In iPad Settings, Bluetooth is on, but the little “wheel” just spins and spins unable to locate any devices (Fitbit is my only Bluetooth device). When I logged back onto the app, it asked me to allow notifications, which I allowed, but never asked me about Bluetooth. I’ve tried restarting both my Fitbit and iPad several times, but nothing works.
10-10-2019 04:14
10-10-2019 04:14
Hello @VickK
I see your having trouble syncing your Charge 2 to your iPad Bluetooth. I would suggest you restart your Charge 2. You can see how it’s done here: https://help.fitbit.com/articles/en_US/Help_article/1186/?q=Restart&l=en_US&fs=Search&pn=1
You might have to perform this restart several times but hopefully this will do the trick 😃
10-10-2019 16:23
10-10-2019 16:23
Unfortunately, as I mentioned in my previous post, I did try restarting both my Fitbit and iPad several times, and this didn’t work. Contacted Customer Support, but got a boilerplate response that told me to try all the things I’d already tried. I’ve since tried syncing on my Windows laptop and this works fine, so definitely an Apple/iOS issue.
Thanks anyway!
10-13-2019 09:06
10-13-2019 09:06
My wife has an iPad Pro 10.5 and afyer the update to iPadOS was getting the message that Bluetooth was not turned on.
Logged out from her account, removed the app, restarted the iPad, reinstalled the app, logged back in, and then got the prompt to allow access to the Bluetooth. Added the Charge 2 back in and everything is working well again.
Thank you.
10-13-2019 09:34
10-13-2019 09:34
This is outstanding @Steve-Brampton
Happy Stepping
10-13-2019 12:39
10-13-2019 12:39
Hi Steve-Brampton. Thanks a lot for your reply. Unfortunately, I tried that multiple times, but my iPad Bluetooth still wasn’t finding my device. I wasn’t getting the notification to allow Bluetooth whenever I reinstalled the app. A few back and forth emails with Customer Support and my Charge 2 seems to be syncing again, at least enough to keep my stats up to date. (I don’t think it’s actually anything I did, because they were suggesting things I’d already tried, so I think they got some bugs worked out on their end. They were very good about getting back to me quickly each time and I could see they were specifically working with trying to sync me from their end, which finally worked.)
When I go into iPad Settings, it still can’t always find my Fitbit. But with my stats updating regularly, I consider the problem solved.
One thing Customer Support suggested - and this may be relevant for anyone still having problems - was updating my Fitbit firmware, which they said was not up to date. I’m running 22.58.0. Can anyone tell me what the latest version is? Usually, if there’s a newer version available, I get a message on my Dashboard and follow instructions to download it. I can’t seem to find anything anywhere that lets me download a newer version.
Thanks!
05-26-2020 16:27
05-26-2020 16:27
i tried this several times on my iPad and it did not work. It says Bluetooth is connected to charge 2, but nothing is recorded. Nothing has been recorded for two weeks. No help when I contacted Fitbit. This is discouraging!
11-27-2020 20:35
11-27-2020 20:35
Many thanks - this solved the problem. I was on a 26-day run of >5 mi/day, but not being able to sync broke the string yesterday. even though I walked 5+ miles.