Android 9.0 (Pie) not able to sync

[AlessFitbit]

Fitbit Update: 3/6/19

Hello everyone! 

We have some updated troubleshooting suggestions we'd like for all of you on Android Pie (9.0) to try. 

First, turn off Background Restrictions/Limitations: Phone settings > Apps & Notifications > Fitbit app > Background restrictions or Background limits.

Then, disable battery limitations:

1. Go to Settings > Apps > Fitbit app > Advanced > Battery > Battery optimization
2. Change view to All apps
3. Search for Fitbit app
4. Choose Not optimized

Please give the steps above a try to improve syncing with your Fitbit device and Android 9.0 OS. We're still researching and testing out long-term solutions to this ongoing syncing issue. We thank you for all your patience while we continue to work on this effort.

---

Fitbit Update: 2/14/19

Hi everyone!

Thanks for all your reports and patience with these Android 9.0 syncing difficulties. We’re aware of this ongoing issue and have been working to identify a resolution as quickly as possible. 

We're sorry for any trouble. We appreciate your patience and look forward to getting you back on track as soon as possible. 

I'll let you know if I receive any additional information on this matter. 

---

Fitbit Update: 10/3/18 

Hey Everyone!

Our team is still working on implementing a longterm fix for syncing with Android devices on Pie (9.0). 

For the background syncing issue, I have posted an update in the other floated thread which you can find here. 

We released Fitbit for Android version 2.80 today which contains improvements for that syncing issue. 

I'll make sure to keep you all updated with more information, as soon as I have it available. We're still working on this and I really appreciate everyone's patience. 

---

Fitbit Update: 9/26/18

Hey everyone! 

Thanks so much for your patience and cooperation. We are aware of the issue and working with Google on a solution.

I will continue to provide updates here, so keep an eye on this thread. 

---

Fitbit Update: 9/10/18 

Hi, everybody! 

Thanks for your patience while our team continues to work on improving syncing for those on Android Pie (9.0). They are actively working on this and for the time being, I recommend you keep the Fitbit app updated on the latest version for best syncing results. Right now that is version 2.78, so if you're not on this version please update! Also, another troubleshoot we recommend is performing a restart on your phone. 

When there are more improvements made in the future I'll announce them here. Stay tuned and subscribed to this thread. 

---

Fitbit Update: 8/19/18

We have escalated these syncing issues for those who are now using Android Pie (9.0) to our team for investigation. There aren't any updates at the moment, but rest assured we will keep you informed in this thread when more information is available.

Thanks for your patience! 

---

Fitbit Update: 8/11/18 

Hi, everyone! Thanks for stopping by the Community Forums. 

Seems like many of you who updated to Android Pie (9.0) are now having trouble syncing your Fitbit trackers. I'm going to escalate this to our team so they can look into it.

In the meantime, please update the Fitbit app to version 2.76.1 if you haven't yet. Let me know if that changes the syncing behavior. Please follow this thread for updates. I'll keep you all posted here! 

[LanuzaFitbit]

Hello everyone.

Thanks for sharing your experience on the matter.

Thanks to all of you that are sharing the steps that have been followed to get it to work. 

If you have not tried them already, be sure to try the following steps. It is possible that they could help in getting it all to work.

As mentioned above, working to identify a resolution as quickly as possible. 

We're sorry for any trouble. We appreciate your patience and look forward to getting you back on track as soon as possible. 

Let me know if you have any further questions.

[AgentOrange]

What seems to have fixed this issue for my girlfriends SGS 9+ (Pie with february patch), was to go into settings -> app permissions -> and remove the "location" permission of the fitbit app. After that i restarted the app and was greeted with a "location permission required". After accepting sync worked immediately.

[mattdm]

I just tried this with my Zip and, unfortunately, no change. Still doesn't sync until I pop the battery out and restart (and then that doesn't last).

[AgentOrange]

On further thought, maybe it was a combination of things i did (before googling and landing on this forum):

1) un-paired the charge 3 on bluetooth screen

2) tried to re-pair (didn't work)

3) uninstalled fitbit app

4) reinstalled fitbit app (no change still)

--- here i googled and found out that this is a wide spread problem ---

5) remove location permission

6) re-started the app 

7) get asked for "location permission" OK  and after that "pair with fitbit charge?" - OK

😎 sync worked again (first time after 5 days and several restarts of the phone, charge, etc.)

[cathie-c]

This may seem overly simple, after having spent hours tonight trying to sync my blaze with pie, I remembered something from syncing my old charge, make sure you have nothing else connected to Bluetooth, as soon as I turned Bluetooth off on my ipod my blaze synced to my android pie straight away. 

[SunsetRunner]

I am sorry but I am passed the point of patience, it has been moths for this thread and a month for me.

I have tried all of the methods below and all they have caused me is grief. The last one recommended deleting my Ionic from the fitbit app and reconnecting. This was a disaster the only way I could reconnect it was to dig out my old phone that is running Android 8 and use that to re-add and sync it. Since then on a daily basis is have to reset my phone and every 2 days I have to revert back to my old phone.

The annoying point is that the app seems to connect every now and again, and update some of the data. Currently my steps are 1000 out, my floors are what they were at 9am this morning (it is currently 3pm) and my morning activity has not been picked up yet. Also even though the steps are not far out what is uploaded is miles out and the even though the steps wee synced 10 minutes ago the synced today figure is 3 hours out.

There is obviously a lot of work needed with the latest version of android but a company the size of FitBit should have the manpower to deal with it.

Damion

[zsk240]

Agreed, I found that Bluetooth only allows up to 4 devices at a time to sync with your phone for instance. So I check how many are syncing with my Pixel IIXL and if it is four, I delete one and suddenly it will sync with my Fitbit Versa.


Sent from Mail for Windows 10

[idilham]

Hi Aless,

Is there any progress? I have been waiting it to be fixed as until now I cannot sync my Versa with my Android Pie. Any timeline by when it will be fixed? Thanks!

[Muerte55]

Is this at all related to why it asks me for my login name and password, and after entering the correct information, it tells me its wrong? I was synced fine for a long time. Is this bump in the road just recent, mine quit syncing 2 days ago. Very frustrating as this made it very easy logging food in by scanning barcodes. Anxiously awaiting the fix.

[Acid0057]

So I was able to finally get my Fitbit Versa to sync and work with Notifications, SMS replies and Calls on Android 9 February update on my Pixel XL 1.

Before I had formatted my phone, factory reset the Fitbit Versa, uninstalled the Fitbit app, etc and none worked. I think my steps below combined with a Fitbit app update and maybe Google Android OS update have fixed it finally. It's been working for the past hour pushing phone notifications to the watch consistently along with syncing steps, heart rate, etc. Did a ton of Watch app updates too.

Android OS: Android 9.0 Pie with February 5th Security Update

Fitbit Version: 2.87

Here are my steps:

1. Go into the FitBit apps Info page. Either hold down on the Fitbit App Icon and open Info or go via Settings>Apps & Notifications>See All Apps>Fitbit

2. Tap on Permissions 

3. Revoke all permissions

4. Press Back Button to go back to the Main Fitbit Info screen

5. Force Stop the App.

6. Go into the Bluetooth settings and Forget any Fitbit Trackers (I forgot both my Versa and Versa (Classic))

7. Reboot your phone

8. Shutdown your Fitbit

9. Log back into your phone (I have mine encrypted so I have to login before the phone fully boots)

10. Start your Fitbit

11. Wait till both are started fully

12. Try to force a sync.

Took a long time on that first sync and now its sycning consistently. Did all those updates and added in my Wi-Fi to the Versa. Working great now! Fingers Crossed will update if anything changes in the next few days.

I'm sorry but I think something similar was posted a few weeks back as a fix but at that time it didn't work for me at that time.

Hoping this helps someone. Also hoping that Fitbit is somehow able to test this and get the word out to people not watching this forum.

So I got that fixed and now when I reply with a Quick Reply on the Versa to a Text it sends 7 replies at the same time! Fix one problem find another 🙂 At least it syncs now!

[Tiabessa]

I've been having difficulty as well with both my Charge 2, Charge 3 and my Galaxy S8. I have to log out of the app and hope that it asks me to link to either of them. I keep getting requests to restart Bluetooth. This is ridiculous, it's been Months. 

[LanuzaFitbit]

Hello everyone!

@Acid0057, thanks for sharing those steps that ended up helping you out.

@Muerte55 This would not be related to the issue that you are describing. In your case I'd recommend that you try switching from your WiFi or mobile data to the other. That should help so that it lets you log in again.

Our team is still looking into this situation. We hope to have you all back on track as soon as possible.

Feel free to reach out with any other questions.

[Acid0057]

Hi @LanuzaFitbit thanks but I'm sorry to say that it didn't last. My Fitbit Versa has stopped syncing as of this morning. I can still sync via Bluetooth or the Fitbit Dongle on my Mac and PC but cannot sync on my phone anymore. It lasted for maybe 6 hours before stopping. All that time my Google Pixel XL 1 and the Fitbit Versa were no more than 10 feet apart. Now my Versa refuses to connect at all to the Pixel XL.

Hopefully, that helps in troubleshooting. I should also bring up that we have a Google Issue Tracker open at: https://issuetracker.google.com/issues/123997469 

More people that get onto the tracker and Star the issue and comment the more Google will also look into this on their end as well. 

[mattdm]

This is part of the frustration with what you keep telling people. All of these hoops you asking us to jump through are a lot of work for users, and some of them (like clearing network settings) are destructive (now you've got to re-collect wifi passwords). That's super-annoying when Fitbit should be doing the reproducing and testing. Just get yourself a Google Pixel and a Fitbit Zip and watch it not work.

[Muerte55]

I found a fix a couple days ago under Charge 2 from another user. I am good
to go !!

[snehamadinur]

Sorry to come across as blunt, but isn't it disappointing that fixing something which is a pretty basic feature is taking this long? You guys are way smarter than I am, but don't you think it would help if you could at least provide a tentative timeline on when you expect the fix to be tried out?

[ChipCharge]

The Google Tracker URL above is incorrect--the text is right, but the actual link has bogus characters and is a dead link. The correct link is: https://issuetracker.google.com/issues/123997469

If this involves a Bluetooth LE bug in Pie, it is important that everyone star the issue in the tracker so that it gets google's attention.

[SarveshK]

It's been loooooong enough we are facing this issue. And Fitbit is yet to find a permanent solution for it. Aren't they capable?

[Acid0057]

Oops, that was my bad. I had an extra space at the end of my pasted URL.

Thanks for correcting that @ChipCharge 

We have 24 stars and it has been assigned to an ASOP engineer to look at. Please go and star, like ChipCharge said. More stars, more chance of it getting a closer look at Google.

[WarAxe]

I have to echo everyone else's bluntness.  This issue was identified over 6 months ago.  You are stringing people along with "we're working on it" and "thank you for your patience" without committing to a time-based solution... without a commitment to your customers.  You're also having people perform actions you know to be temporary.   

That's not acceptable. It's been over 6 months. Your management owes us a better explanation, an apology for their service lethargy, a time-based commitment for a fix, and a compensatory gesture in the meantime.