06-27-2020 10:22 - last edited on 06-28-2020 14:37 by LiliyaFitbit
06-27-2020 10:22 - last edited on 06-28-2020 14:37 by LiliyaFitbit
Hey People,
I am having some problems with logging new foods into my app on my Iphone, It does not give the option to enter a decimal point meaning you would have to round the figure up which means all the macros will not be correct.
My fitbit app on my iphone and my IOS is all up to date and i have cleared any cache files to see if that will help at all.
I know 18months to 24months ago it used to work when i first got my Fitbit blaze as i created a few new meals that i was eating at the time.
If anyone knows how to rectify this issue please let me know.
Reagrds
Scott. UK.
Moderator edit: subject for clarity
06-28-2020
14:35
- last edited on
09-14-2024
10:01
by
MarreFitbit
06-28-2020
14:35
- last edited on
09-14-2024
10:01
by
MarreFitbit
Welcome to the Fitbit Community, @Scotty2020.
I appreciate your participation in the Forums and sharing your concern about the option to enter a decimal point when you log new foods in the app. Thanks for trying to resolve this, I appreciate the additional details and I am here to assist you. Our team is always working on improving our devices and user experiences, and your comments are always welcome.
While the option for decimal point is not available at the moment, feel free to post your idea in our Feature Suggestions board. That way other users can comment and vote on the idea to show their support. Please check the FAQ to better understand how that board works. You can do a search first, in case someone else has already suggested your idea, or something similar.
Let me know if you have any questions.
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
06-28-2020 15:58
06-28-2020 15:58
I must beg to differ.
This request by @Scotty2020 is much less of a Feature Suggestion than it is a "Bug Report".
If I remember correctly, as others have stated, the control used to present the "ten-key" in the past incorporated a decimal point and has been replaced with a control that does not.
After 40 years as an IT professional, I have to say that the unplanned loss of functionality is a bug that has to be laid at the feet of the developers - - - unless of course they were directed to incorporate that loss, in which case the responsibility rests up the chain.
Either way - gotta be classified as a bug.