Unable to log water with Today tab shortcut

[carsito]

Is anyone else experiencing issues with FitBit's iOS app (Version 4.39) in logging the amount of water consumed throughout a given day? The 'plus' sign located at the bottom right-hand corner of the main UI used to function flawlessly, allowing me a short cut to enter oz of water consumed. All of the sudden, the top bar where it says "Save" or "Cancel" has disappeared. Once I attempt to log via the plus sign, it will not allow me to cancel, so I have to manually close the app.

 

Moderator Edit: Clarified subject

[Jeff-in-NC]

There’s a thread about it with an update from a moderator. It was escalated to developers on Thursday. https://community.fitbit.com/t5/iOS-App/Previous-water-log-units-changed-to-oz/td-p/5738992/page/2 

[Walker123456789]

But the last data before 4/1/2025 is all wrong. It’s the correct value in ml, but I logged in oz. When will this be fixed?!? I’m supposed to be tracking for the doctor and now it’s all gone! 

[WayneOz]

I like you, LizzyFit, have just yesterday on 4/5 earned my 9 year anniversary badge. Thank you Fitbit for reminding me that your update on 4/3/2025 caused me to lose 9 years of water log data. 

To clarify, as 4/6/2025, no, my historical data has not been been recovered.

 I’m surprised that Fitbit doesn’t have a “sandbox” environment to test program updates.

 I’m more surprised that the programming team cannot perform simple mathematical conversions of ounces to milliliters to ounces. 

The Fitbit community is very disappointed with the programming/software development teams performance and their inability to fix the mathematical error as soon as it became apparent. 

[LizzyFitbit]

Hi everyone, and welcome to our new members.

Thanks for your continued reports. I'm closing this thread to further comments since the issue of the Today tab shortcut not allowing water intake logging has been resolved.

I want to let you know that we've escalated the unit of measurement issue to our team. I apologize for this inconvenience, your feedback and patience are truly appreciated. Please follow this thread for future updates on that issue.