06-08-2024
10:41
- last edited on
06-09-2024
09:46
by
MarreFitbit
06-08-2024
10:41
- last edited on
06-09-2024
09:46
by
MarreFitbit
I know this is a common thing, but like everyone else, I’ve tried all the steps.
My Inspire 3 hasn’t completed a sync since May 25, 2024.
I’ve restarted the device; restarted my phone; disconnected Bluetooth and repaired; deleted the app and reinstalled and ensured it is up to date.
When I tried to contact support via chat, I was connected to an agent twice but each time, the app crashed and I was disconnected. I waited over 20 minutes for each and had to make sure I kept the app open. Despite those efforts, the app still crashed, and I lost connection.
I don’t want to delete the device from the app because I could lose all the unsynced data.
Moderator Edit: Clarified subject
Performing a Factory Reset on the device would recover your device, but you would lose the data that is on the device. However, this might work, with no data loss.
I woke up this morning, and it was suddenly working. I’m glad, but this is what happened right before my Inspire 2 died. I don’t think I’ll be buying another FitBit. The best they ever made was the Flex 2. Man, I loved that little tracker.
Best AnswerMy Inspire 3 quit syncing when the app updated from 4.16 to 4.17, but I was able to resolve the problem that time by restarting the Inspire 3.
I probably should have added a 'Restart device' step after the unpair device from the phone step above, just to make sure that there was no leftover BT info on the device from when it was paired before that would cause problems when repairing it later.
Best AnswerI have had the same issue for at least six months and have spent the time to walk through all the recommended steps provided in this forum (including from the moderator). Prior to purchase by Google my Fitbit was rock solid. Since then it has become a very hit and miss application. We should not have to keep reinstalling for this to work.
Totally agree.
The device setup process should be as 'frustration free' as possible for the customer and that certainly isn't the case with these devices. The Google FW/SW development teams should start putting a little more effort into doing that.