08-11-2018 14:07 - edited 09-12-2019 10:48
08-11-2018 14:07 - edited 09-12-2019 10:48
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:
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!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
Answered! Go to the Best Answer.
10-30-2018 11:02
10-30-2018 11:02
10-30-2018 13:00 - edited 10-30-2018 16:18
10-30-2018 13:00 - edited 10-30-2018 16:18
I am very hopeful! I just installed the latest update and I've been able to sync for the past 30 minutes! 🙂 Note,I have a Pixel on 9 pie with an original flex.
😞 Sadly, my Pixel was not able to stay connected with my Fitbit flex. PLEASE keep trying to fix this for us. The message I keep getting is "could not connect with Flex."
I am on version 2.82 of the Fitbit app.
10-30-2018 13:15
10-30-2018 13:15
@Cookiemom4 wrote:I am very hopeful! I just installed the latest update and I've been able to sync for the past 30 minutes! 🙂 Note,I have a Pixel on 9 pie with an original flex.
Which version is the latest update? My Fitbit app is version 2.81 and I have been running into a whole mess of syncing issues with my Versa and Pixel phone (running Android Pie).
I recently got a new Versa (old one had a screen issue), and after setting it up with my phone I can no longer sync in the background with my phone. My previous Versa was set up with Android Oreo (in May 2018) so it was successful. Ever since trying to set up on Android Pie, it only syncs the first time and I would always have to force close my Fitbit and open it again for it the sync.
10-30-2018 13:52
10-30-2018 13:52
It didn't seem to help with my One. I reset the One this morning and got one or maybe 2 syncs. I've just rebooted my phone, and no sync. I suppose I'll try both later tonight or tomorrow after I charge the One.
10-30-2018 13:57
10-30-2018 13:57
Just updated to 2.82 on Pixel 2 XL with a FitBit Zip. No luck. Cannot pair it through the Bluetooth settings or through the app.
Earth to FitBit.
10-30-2018 15:29
10-30-2018 15:29
My issue (since August) seems to be resolved with 2.82/Pixel/FB One. Sync has been normal for an hour.
10-30-2018 15:56
10-30-2018 15:56
I updated, started the app... immediately, "Tracker not found."
FitBit does not fix their bugs.
10-30-2018 16:06
10-30-2018 16:06
Restart your Fitbit device? That's when mine started clicking post-update.
10-30-2018 16:24
10-30-2018 16:24
@tofuuu630 Unfortunately, my Flex did not stay connected to my Pixel. I had updated to the 2.82 version of the Fitbit app. Soooo disappointed! I don't understand why they don't make the Flex maintain a connection with our phone, as they do for other Fitbit trackers! This seems to be the problem, as the message I keep getting is "cannot connect with Flex." This error message occurs when I manually attempt to link the Fitbit with my phone after I have requested a sync. Sorry to be the bearer of sad news.
10-30-2018 16:24
10-30-2018 16:24
I installed the Fitbit app update (version 2.82) on my Pixel 2 XL (running the latest version of Pie), powered down my One (by plugging it into the charging cable while holding its button in), restarting my phone, and the powering up my One (by removing it from the charging cable and pressing its button until the firmware version appears). Doing this, and then launching the Fitbit app on my phone caused my One to sync within a few seconds, and I was able to perform a sync on demand a few minutes later.
Now to see if this continues for more than an hour or so...
10-30-2018 16:25
10-30-2018 16:25
Please update us and let us know if the connection continues. Mine no longer connects after an hour.
10-30-2018 16:32 - edited 10-30-2018 16:35
10-30-2018 16:32 - edited 10-30-2018 16:35
Have you tried factory resetting THE TRACKER?
I proposed many times previously:
- forget the tracker by the app
- factory reset the tracker
- delete apó data
- delete app
- install the app
- install the tracker in the app as a New device
10-30-2018 17:09
10-30-2018 17:09
@Cookiemom4 it's okay, sad news and Fitbit goes hand in hand so I expected it lol.
10-30-2018 17:27
10-30-2018 17:27
My 2.82/Pixel/FB One connection finally perished after a few hours. Longest I've stayed connected since August. Not a permanent fix, though.
10-30-2018 18:57
10-30-2018 18:57
Just updated to the latest version 2.82. Just noticed they pushed an update just before November 1, and noticed their API is still targeting Nougat (25). Google requires all apps listed on the Play Store to be at least API 26 (Oreo) but I don't have my hopes up for Fitbit to do the same. They're the only app on my phone that is below API 26 and is a huge drain to my battery. Annoying...
10-30-2018 19:33 - edited 10-30-2018 19:34
10-30-2018 19:33 - edited 10-30-2018 19:34
Your post made my curious so I downloaded an app called AppChecker (I use Pixel 2 XL with Android 9 hence API 28) and here are some samples:
- Runtastic API 28
- Fitbit Coach API 27
- Pocket Casts API 27
- Telegram API 27
- Fitbit API 25
- Hangouts (by Google) API 25
- Measures (by Google) API 25
- Allo (by Google) API 25
- Strava API 25
- Paypal API 25
- Google Opinion Rewards (by Google) API 23
So it seems Fitbit is in good company, even by Google itself
10-30-2018 19:46
10-30-2018 19:46
@Giampi71 lol I guess because I don't have any of those apps on my phone which is why I'm not seeing it. But yeah, I think there is a reason why they updated Fitbit today. Probably won't be seeing an update for this app for a while..
10-30-2018 19:51
10-30-2018 19:51
The worst app in my system:
Seesaw Family (seesaw.shadowpuppet.co.seesaw)
App Version: 6.0.4 (14790)
Installed: Sep. 4, 2018 06:10:21
Last Updated: Oct. 10, 2018 07:10:43
Target API: Jelly Bean (API 17)
Min API: Kit Kat (API 19)
Aaargh!
10-30-2018 19:54
10-30-2018 19:54
@Giampi71 oh my lol... Haven't seen those kind of API in years! Please tell me the developer hasn't updated this app in years right?
10-30-2018 19:57