04-21-2025 23:07
04-21-2025 23:07
I've been trying to edit the start and end times of a run, as Fitbit incorrectly logged it in Auto mode. I can click on the Pencil icon to edit it and change the data in the boxes, but when I hit the Save button in the top right corner, nothing happens.
Please fix - this app is so broken and full of bugs I haven't got the time to report everything, but this one is important.
I've been a loyal user of Fitbit since the original Charge - now I'm looking at alternatives which offer a better user experience. Since Google bought out Fitbit it's gone down the pan. Incidentally I won't be including any Google product in my shopping list.
04-25-2025 19:27
04-25-2025 19:27
Welcome to the community, @Ibiki.
Thanks for letting me know about this situation. I understand where you're coming from and I apologize for the inconvenience this has caused. Our team constantly works to improve our devices and services, and comments like yours help us to make that happen.
To work on this together, I recommend trying the following steps:
04-26-2025 02:19
04-26-2025 02:19
That doesn't work anymore. Been doing that almost daily and problems still occurring. These moderator copy/paste answers are worthless. Google needs to fix this ASAP.
We can no longer trust that our Fitbits or the app are accurate. Users stats are getting more and more corrupted everyday and Google has done nothing.
05-09-2025 09:55
05-09-2025 09:55
Hi there, @TheNeilHaley.
Thanks for taking the time to share your feedback regarding the Fitbit app. I understand where you're coming from and I apologize for the inconvenience this has caused. We're always working to improve our products, and the input we received from our members is a big part of the process.
Regarding your concern, let me share with you that the issue with the Save button not appearing when logging water was already fixed by the team. However, if the issue persists on your app, let me know the model and software (OS) version of your phone.
06-03-2025 16:30
06-03-2025 16:30
Hi,
The bug is still reproducible. Any update on this? Please send an ETA for the fix. Thank you.