10-24-2023 07:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-24-2023 07:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Error found (bug in app program)
1) Dashboard error on the food dial. The food dial doesn't correctly update past and present caloric intake when aiming for a traget. The dial is abnormally over or under the the graph (in the food tab is displaying a green bar).
2) Food figures False Please Please update your code in the food tab. The current weekly food intake takes an average for 7 days and not the number of days passed (plus the current day) for this week, resulting usless info...
EG: Today is Tuesday and my average caloric average intake for this week displayed 600 cals and in reality it's 2500 kcals...
I dont know how to tell the developers and as a developer myself this is very poor practice to let this slide past software testing revisions. Its one line of code to fix this. It's simple, thr average for this weeks food in divided by the number of days past!
Please check if I'm wrong.
Who else has this problem?

- Labels:
-
Health Metrics
10-25-2023 22:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


10-25-2023 22:40
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @eVade - thanks for the info which have already been signalled along with many issues with the new app.
Probably best to post in "The redesigned Fitbit app is rolling out!" topic in this forum along with the other unhappy users where you will see more fully the issues.
Unfortunately it would seem likely you are stuck with this version officially. Though there may be some tweaks over time already mentioned there, it could take months to get the current test version working to the same level as the previous version 3 app.
Author | ch, passion for improvement.

10-26-2023 08:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-26-2023 08:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I have similar problem.
App version is 4.02.1
This is a core functionality, and tbh it is inacceptable.
