07-23-2022 09:00 - edited 07-24-2022 05:55
07-23-2022 09:00 - edited 07-24-2022 05:55
07-24-2022 06:57
07-24-2022 06:57
Quick add calories are delayed to show up in the left to eat calculation.
07-24-2022 12:57
07-24-2022 12:57
Mine was broken for ages, then seemed to get better (but gradually, not suddenly). Then for a week so it was finally working properly. And now it's broken AGAIN, after people have been complaining about this for literally months. My entries (quick calories) are not registering, and with the forced update, now the 'calories in vs out' graph doesn't work like it used to - I can't open it up to actually see the specific numbers. All there is is an unclear little bar chart, but what I want is to see the actual numbers like before. Why did they change it?? It was fine before. And not having the foods register AGAIN is just so frustrating. My bf bought me my FitBit last year, and while the device is generally good, the app is often useless, but the former is useless without the latter. Another issue I've had when exercising is the GPS suddenly stopping tracking, so my distance is well below what I actually did, even though it keeps counting my steps and time, so frustrating.
07-24-2022 20:32
07-24-2022 20:32
Having the same issue.
Quick calories disappear from the app almost immediately after entry. On the website, they affect the total (massively inflating it when you, of course, try to add the calories several times in a row because of broken non-idempotent entries...) while being completely absent from the detailed list.
This smells like database problems. It's been happening sporadically to me for years.
They need to fix this problem permanently.
07-25-2022 16:31
07-25-2022 16:31
Agreed, also after synching, the "calories burned" updates without updating the "calories remaining to eat" number. Only way to to upadate "calories remaining to eat" is to click the tile and hit back button and sync again.