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! 

[Asr1989]

I have updated to the latest version and it still won't sync. When will this be fixed?

[Gusthy]

I don't want to be the bad guy again, but the target API level doesn't mean almost anything, and an app (or a company) is not good or bad if it this value is big or low. 

Very minor changes might occur on the appearence of the app based on target SDK, it doesn't refer to the used APIs.

[SunsetRunner]

All an API level changevmeans is that the source was compiled with a higher API level.  It does not mean any source code actually changed.  It can be done just to keep the app on the Google store.

[Gusthy]

It is tricky.

There are three API levels:

- Minimum API level or minimum SDK: this tells what minimum Android version is required to run a given app. If a device has lower API level, then a given app with higher required API version won't install/won't appear on Play Store.

- Target API level or target SDK: an API level that tells which Android version is the given app intended to run. It has rather low impact from the end user's point of view, but requires quite an extensive testing.

- Compile SDK: tells what version of Android software development kit is required to compile a given app.

It is generally true that Minimum API <=Target API <=Compile SDK.

The policy is that all existing apps in the play store can publish updates as a minimum of _target_ API 26 (Oreo) from 1st of november. Technically it can be done by modifying a manifest file in the source, it will work as previously. Android itself will use this info only in a very limited way.

[sueb859]

Did the latest update for my One on Pixel 2 XL and was very encouraged.  After reboot last night it seemed to be working.  Until this morning when it stopped again.  This is just ridiculous.

[SunsetRunner]

And...about an hour after all that updating and restarting and successfully syncing my One, all syncing (both automatic and on-demand) fails with the usual "tracker not found" error.

Just like it's done since August.

[cmegli]

I just got a Pixel 3 and my Fitbit one will only sync for a few minutes after I reset it. I have to reset it every time I want to sync.

[NotATech]

An update to my sync issue: I uninstalled the Fitbit app and when I reinstalled it there was a new version (2.81) that installed. My Fitbit Alta HR has been connecting and staying connected to my Bluetooth and syncing with the Fitbit app consistently. I looked up the Fitbit versions available and noticed there are two that were released on 10/16 (2.81 and 2.81.1) and on 10/29 version 2.82 was released. Since mine is now working fine, I'm almost afraid to update to the newest version! I will probably wait a few days before trying.  

[jmichaelkramer]

I updated to 2.82 released 10/30 and my fitbit one started syncing.  

I got excited and almost ordered a Charge 3.

This excitement lasted for  only an 1:15 minutes.

It synced multiple times.

During that 1:15,  I was still getting the notification, "Linking with Fitbit app required for connectivity".  

Seems like I need to continue to be patient.

[Gusthy]

It seems that the problem is device dependent now.

A I see, One is problematic now  Versa and some newer devices are not.

IT would be nice if Fitbit would confirm or reject this ecprience. 

[cmegli]

Mine synced for about an hour after the last reset. I thought it was fixed,
but isn't syncing now.

[Gusthy]

What tracker it is? 

[cmegli]

One

[SunsetRunner]

@Gusthy brings up a good point about how the problems might be concentrating more on the One now, though I think it would be a worthwhile exercise to gather a bit more data. So, to that end:

Anyone who is still having sync problems with the latest version of the Fitbit app (which is presently 2.82) and who has a tracker that is NOT a One, please make yourself heard by replying to this post.

[AdamH0]

Pixel 2XL. Android 9, 5th Oct Update

Fitbit One: 6.64

Fitbit App 2.82

Cautiously believe it might be working...

After a sync via Windows 10 app I was able to sync the One via Android (slowly).

It has been doing this for over 12 hours now and I've synced multiple times.

I have not restarted the One for several days (and this used to be the only workaround for syncing via Android 9).

I will soon test a phone restart and a fitbit restart to confirm they keep working.

I'll provide an update in a few days to see if this stays working, or stops. 

[Cookiemom4]

I have a Fitbit flex and a Pixel on 2.82; syncing is still not happening. Tracker cannot be found.

[Rho1029]

Updated to 10/29 release on Pixel 2 and still nothing.  It has been almost 3 month.  My wife gave up on her Fitbit last month, I'm about to as well.  

[DennisO]

I have a onplus6 on Android pie and syncing hasn't worked since I upgraded weeks ago...

I assumed this would be fixed quickly, but still nothing and there doesn't seem to be any communication around this either. 

[iorbitearth]

The issues at Fitbit are so underlying that leadership hasn't prioritized a fundamental issue affecting the Android customer base. Something isn't right.

[nits]

I don't think so they can ever fix it or willing to fix the issue. I wrote to Fitbit few days back about sync issues with Oneplus 6 and answer I got was, Oneplus 6 is not compatible and supported device. This is what there commitment is. Funny.