Syncing issues after update

[SunsetRunner]

I want to see how many of us are in this community. They can't lie to us all about this in a single thread of people still having this same issue.

At this point it's ridiculous. 

Moderator edit: updated subject for clarity.

[Ruchika179]

It won't sync at all after the app has updated itself!

[JSussick]

Update 9/19:

So this last update helped but each day I still have issues syncing. So to me the issue is still not resolved completely. I even bought another Charge 2 thinking maybe the issue is with our old Alta versions.

[Trainer_84]

WHEN IS THIS GOING TO BE AVAILABLE ON THE GOOGLE PLAY STORE? THIS IS FRUSTRATING AND UNACCEPTABLE FOR THE HIGH PRICES YOU CHARGE FOR YOUR PRODUCTS!!

[Poussun]

I updated the app with the latest version, and the Versa firmware.... and it is worse than ever !!!

The Versa is not recognized on Android (event after a Samsung reboot)

In the past, I was able to sync on Win10... and now the Versa is also invisible in Windows

What a disaster development team !

[SunsetRunner]

Well, I upgraded to the Versa 2 and have had it for 4 days. I have had continued syncing issues with this new device (similar to my previous Versa) -- "device not found" and "looking for device" keep popping up. And this is on a 2 month old Google Pixel 3 phone. So what's the deal? This is unacceptable!

[jaymz462]

Same issue here, using the most current version of the app.

[Beryllyford]

The only thing I could do is upload the Fitbit app to my iPad to see my data. It won’t sync to my Android phone, a Samsung Galaxy 7 Edge. Not happy that I can’t have it on my phone. I hope the developers come up with a fix soon.

Sent from my iPad

[LostEchoes]

New version 3.6.1 of the Fitbit app is now on Play Store. Has anyone installed it to see if it fixes any of the known issues ?

[dewpie56]

I did. Just updating the app didn't fix things, sync was intermittent at the very best, usually after unpairing all other Bluetooth devices and restarting the FB. But, I got a firmware update last night for my Versa, and though it took awhile because of the connection issues, it eventually got updated. Once I restarted everything, its been syncing much more reliably, though still not perfect; I still get device not found fairly often, but then it will sync after a couple minutes. So, progress has been made, but they still have a ways to go before I'll ever consider buying another Fitbit product.

[Poussun]

After a couple of 'reboot, bluetooth on/off, Versa factory reset, resync...', I managed to have the Versa working fine on Windows 10 App.

The watch is sometimes detected on Android, but the installation fails, always. 

The brand new version of the App and the new firmware are NOT solving the sync issue.It even creates more issues.

[LostEchoes]

On you phone try to go within the Settings -> Apps, find the Fitbit app and delete / clear the App's Data and Cache. Then Uninstall it.
Reboot your phone and then download & install the Fitbit app 3.6.1 (latest) from the Play store. That might help even more.

[Poussun]

I deleted the cache, the application, reboot, re-installed... The Versa was back... during 1h.

Android Sync is lost (again)

[LostEchoes]

@Poussun 
This is outrageous. Their 3.x android app versions have only brought problems and issues that people should not have to deal with. 
Have you tried installing the 2.95 version of the app ?
Some people have found that it works without problems.
You can find it by googling "fitbit 2.95 mirror" (without the quotes).
Before you do that, make sure you follow first the above procedure, delete the current version's cache, data and then uninstall it. Reboot your phone and then install 2.95.

[Poussun]

@LostEchoes 

Thanks for the suggestion, but this is a Professional smartphone, and "external app" aren't authorized (security reasons)

[SunsetRunner]

@LostEchoes I tried what you suggested - cleared cache, uninstall app, restart my phone and add the app again - now it can't even locate my Versa 2. This is crazy. At least the goal circles aren't blinking and flickering, but what's the point if it can't locate my brand new device? (I have a new Google Pixel 3, btw)

[SunsetRunner]

After my device went black, they sent me a new one. They're so salty about it they didn't even send a charger or bands, just the Charge 3 face. I haven't had anymore problems. That leads me to believe that a hardware update may have corrupted the devices. I'm on day 4 and it's still working. My device wouldn't do anything. The screen wouldn't light up, wouldn't charge, there's no coming back from that. I strongly suggest letting them know that your device isn't doing anything and get it replaced while you have warranty left. After this one fails don't think I'll be going with a Fitbit again. It shouldn't take months and months to get an item replaced that's not working and under warranty.

[LostEchoes]

@SunsetRunner 
I'm sorry for this.
Do you mean that you installed version 2.95 or just the latest one 3.6.1  again?
I'm asking because I'm guessing 2.95 might not be not suitable for anyone with a Versa 2 watch, as that watch hadn't been released yet when 2.95 was out.

[LynnS69]

Same here!  Has anyone found an answer?  All I am reading are complaints....which I have too, but no resilutions.

[Beryllyford]

I installed version 3.65 because it was the most recent version listed. It seems to work at least for the past hour.

Sent from my iPad

[SunsetRunner]

@LostEchoes  I meant the most recent app. I have tried the 2.95 and that was working well, but it would not allow me to use the Fitbit Premium trial with that version. So I switched back to the most recent version. It has spotty device recognition right now.