The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.
Like others, I am now having this issue as well. Started last night. Any fitbit app on my watch (fitbit today, sleep, cardio load, ECT) closes out shortly after opening
Mine has been broken says day one. I had luck the other day doing the total disconnects, uninstalls, restarts, etc but it broke again recently. Super frustrating as others have said for a launch product. I feel like the premium membership should be extended for those users who still can't use the app on their watches. Debating returning the watch.
Out of curiosity do you use MyFitnessPal or have any other 3rd parties attached to your Fitbit account / data? I'm asking because I heard from a different user who was having the same exact issue that when they disassociated their MFP app from Fitbit and restarted everything, the following week (Sunday) it was working again as expected. Maybe there's some bad data that's written that the Fitbit app isn't gracefully handling and then crashes the sync? I dunno it's just a guess -- but doing the described fixed it for me.
I removed them all and it's still an issue. I think it's related, but the running distance section on my phone app continuously spins and never loads completely as well.
After you removed them from your Fitbit account, I assume you restarted the phone and watch after that too, has it been a week (e.g. things reset on Sunday). If you are in a new week and it's still doing that then maybe it was just coincidence what I did "fixed it." I wish Fitbit/Google was more transparent about what they believe the issues is -- because it's definitely some kind of bug that was introduced recently (based on all the threads that suddenly popped up here and on Reddit).
Fitbit support finally got back to me: Sorry for the delay in responding. Just received an update from our team. This issue is due to recent Android issue we're facing, since GPW3 uses Android as Platform to sync and the issue it's directly with the platform. Our Engineers teams are aware of this bug and are actively working on a fix.
Thanks for that update @NicholasC . Its somewhat contrary to what others inlcuding myself have been told in that it would be fixed today with an update. If only Google had some control over Fitbit and Android and were able to know about changes to the platform so this kind of thing didnt happen!
Thanks for the update. Kind of crazy took this long to get a response. Also as an aside earlier I confirmed when turning off Bluetooth the app doesn't crash, but this is inaccurate. I was just on a run and I left my phone at home and once I completed the run I tried to open the Fitbit app on my watch and it still crashed. My phone was nearly half a mile away
Yeah that was maybe just coincidence. It worked for me and others. Also I wonder if the MyFitnessPal has any merit either or coincidental. It's hard to know since we all left in the dark as to what the issue was.
Wear OS 5 came out today - maybe that's what they're referring to? My watch came with Wear OS 5 already installed (I think all Pixel 3 watches did). No idea.
Same issue, turning off bluetooth makes it work for a few minutes, but then it crashes again even with bluetooth turned off. Force stopping, reinstalling, relinking accounts, unlinking third party connections didn't help.
Thank you for letting us know that the update to the Pixel Watch Fitbit app appears to have resolved the problem with the Fitbit Today app crashing.
I got the update on my Pixel Watch 3 this morning. I'm trying to find out what fixes were included in the update and will share when I have some info. It would be great if the update also fixed the step tracking/syncing issue that so many of us Pixel Watch users experience.
