Recent Android Fitbit Zip App updates are now causing this common problem where it is 'Looking for Device' but inevitably results in 'No Device found' on Samsung Android 8.0.0 devices like the Samsung S7 and S7 edge, until the battery is removed/reinserted on the Zip.
This is not a hardware problem, since syncing via Windows dongle still works as expected and Android comes back to life after Fitbit Zip reset (verified on two different Fitbit Zips and Samsung S7/S7 Edge phones).
[Edit] Additional Info:
Verizon Samsung S7 and S7 Edge (Android 8.0.0/Kernel 3.18.71/Build R16NW.G935VVRUACSF2)
Fitbit Android App v3.3.1 Aug 15, 2019
Best AnswerCould this be the problem? https://www.forbes.com/sites/gordonkelly/2019/06/12/microsoft-windows-10-upgrade-update-security-pro...
I am having the same trouble as hundreds of other users. Cannot sync.
https://www.forbes.com/sites/gordonkelly/2019/06/12/microsoft-windows-10-upgrade-update-security-pro... could this be the problem?
Best AnswerI have an iphone and it is saying I have done more steps than I have done. I done 12.000 thereabouts yesterday and when I put my zip on today it said I had done 18,000. The zip uses resets to zero after midnight but mine hasn't been doing. It looks like they've updated the app and made a hash of it. The dashboard on the app has changed as well.
My zip stopped syncing on 8/19. I tried taking the battery out and putting it back in. It did not sync. I then replaced with a new battery even though the zip showed the existing battery was fine. It then synced but only that one time. It hasn't synced again since. I have an iPhone. I think the problem is on Fitbit's end. Reading this discussion it looks like it isn't syncing for Android devices, too.