06-29-2019 18:53
06-29-2019 18:53
I was having a similar issue - as of today my Versa wasn't keeping time and wouldn't synch. I thought it was bluetooth issue but my other devices work fine synching with my phone (Samsung Galaxy S5). (Since the last (mid June?) update it seems my battery has been draining more quickly and synching has been spotty.)
I just deleted and reinstalled the app on my phone - my clock is now correct again. Fingers crossed?
06-29-2019 23:49
06-29-2019 23:49
@MikkiCoffman it sounds as if you are having a sync issue. And simply saying phone does not give us any info on the phone model.
06-30-2019 08:33
06-30-2019 08:33
06-30-2019 10:20
06-30-2019 10:20
Yes it has been a sync issue all along.
Now removing a non talking tracker from your app is the worst step a user can do. We still have to fix the non sync problem and now Fitbit does not know what tracker it wants you to sync with.
You say it isn't pairing with Bluetooth? I'm not sure what you are referring to since the user can not pair a Fitbit to the phones Bluetooth, this is a job for the Fitbit app. The user is not suppose to pair the Bluetooth.
When it comes to apple I know next to nothing.
First thing to do is remove the tracker from the phones Bluetooth.
Make sure that the Fitbit app is up to date and the phone has been shut down and restarted.
I also suggest shutting down the Versa through settings, help, shutdown.
Now try a setup.
06-30-2019 12:29
06-30-2019 12:29
06-30-2019 22:20 - edited 06-30-2019 22:22
06-30-2019 22:20 - edited 06-30-2019 22:22
A user should not try and should not be able to pair a Fitbit tracker to a phone. This is a job for the Fitbit app.
The user would do an add device through the Fitbit app to setup/connect the tracker to their Fitbit account. Then, if the app needs to pair the tracker to the phone, the app will ask for permission to do the pairing.
The factory reset also removed the Versa firmware update.
A factory reset which removes the tracker from a users account without telling Fitbit, should be the last resort since it usually only adds more problems and is why a factory reset is rarely mentioned as a solution.
May I ask at what step of the setup process does the failure occure?
Since this is an iOS issue and the title doesn't mention the phone type or the subject, I'm not sure if I should move the thread to the iOS board. Where there would be a better chance of getting the attention of someone who understands iOS.
Of course the original poster is able to edit the subject.