Food logs using wrong day

[gringobranco]

For about the last 2 weeks, my Food Log on Android is always 1 day behind -- that is, it logs food *yesterday* even when the date highlighted in the entry for the food item is *today*.

I open the food item detail to log, and the Day section always shows *yesterday* date ... however the calendar to adjust the day shows it as today's date.  For example, today (14 December), logging a food item comes with a default date of 13th December (yesterday)-- even though in the calendar that pops up in the Day section, the 14th (today) already is highlighted.  I have to change the highlighted day to *tomorrow* (15th December) for the food to be logged with today's date (14th December).  This happens *every day*.  

This never happened before 1-2 weeks ago.  I tried reinstalling the app but the problem persisted.

Moderator edit: Subject for clarity 

[RicardoFitbit]

Hi @gringobranco, welcome to the Community Forums!

Thanks for bringing this to my attention and for all the details that were shared in your post, seems odd that the food log feature of your Fitbit app is behaving in such way, thanks for troubleshooting this situation prior to posting. To better assist you with this, can you please let me know which Android mobile device are you using? Does this occur only with food logs or when you try to log sleep or exercise too? If you haven't already done so, please try the following steps:

1. Force quit the Fitbit app.
2. Uninstall the app from your mobile device.
3. Make sure that the Android version is up to date.
4. Reboot your mobile device.
5. Reinstall the Fitbit app.
6. Login using your account credentials.
7. Let me know if the issue persists.

Let me know if you have any additional questions. 

[gringobranco]

Did what you suggested and the issue still persists.

Doss it have something to do with time zone settings and where the app
thinks I am or what day it is? I tried to verify all the places I could
see time zone.

Logging food today 16 December defaults to 15th in the app even though 16th
is highlighted when you click the date for the food log item. I'm on a
oneplus 7 with oxygen OS 10.0.3 (android)

[LCWalker]

I have the same problem here and it didn't work for me too. I'm on Galaxy Edge properly updated and it was working fine before December. I've downloaded the last Fitbit updated and followed the orientations but the log food is still being logged the day before.

[LynnFF]

I am having a similar food logging date issue.  For about the past week, when  I try to log food, it takes me to December 11, 2019.  Today is December  31,  2019.  ??

[gringobranco]

This is still broken for me, exactly as I described. I have to manually
select 1 day ahead of today in order for the food to log correctly.

Moderator Edit: Personal info removed

[Ashley_waldman]

Exact same thing. I tried everything that was suggested. I have a pixel 4.

[JonesN12]

This has been happening to me as well! Seems like it jasnt been resolved and I've tried everything suggested. It is SOO frustrating!!

[gringobranco]

This just started happening again 2 days ago.  Also the daily macronutrients count in the app is now WAY OFF though it is correct in the online dashboard at fitbit.com.  I believe it has something to do with the time change in the USA (DST) given when it happened. Though it is extremely frustrating to have to manually ajust the day of every food entry, and also now to have to open the online dashboard to get the correct reflexction of daily macronutrient intake.  WTF fitbit?

[Anthuan]

This also happens to me. I noticed that opening the food log from the dashboard shows the chart up to yesterday. If I click the chart, then I see the data for today.

I tried: 1 logging out and in the application, 2 erasing the application data, 3 reinstalling the application, 4 rebooting the phone, 5 checking for updates for both app and phone.

Also, if I try to add quick Calories, it always adds to yesterday's log, without a workaround.

[Anthuan]

I reached out to support on twitter. They are all very responsive, very polite, very useless. They told me to repeat the troubleshooting steps already executed as outlined here, then wrapped up with  "sorry your samsung s20+ is not supported". It's a shame we can't reach the competent people in there. It sounds like a corner-case bug, that's for sure, but if we can't reach the people capable of identifying and fixing it, it looks like we will have to endure this until it automagically solves itself.

[GuiParreira]

Same problem here!

[Anthuan]

I was able to find a workaround, in spite of the twitter and email support (who keep going in circles around "device not supported" and "please reinstall"):

1 set the time zone of your phone to a region that does not use daylight savings time (in my case I changed from Brazil to argentina)

2 set the time zone of your account to a region that does not use daylight savings time (in my case I changed from Brazil to argentina)

Brazil has historically been troublesome for DST, so changing to Argentina, that does not do DST, fixed the problem. I can now see the chart correctly and use the form to add food without issue.

I'm sure the problem has to do with time zones, but the email support folks won't even TRY reproduce the error to be able to help me.

I hope this helps other people with the same problem.

Have a good day, and good luck.l

[gringobranco]

Thanks for the workaround tip.  The funny thing is that Brazil moved off Daylight Savings Time more than a year ago -- we don't use it any more.  So whatever database Fitbit is using must be using old data.  Your solution does seem to work for the short-term, appreciate it.  It also (I hope) will fix the issue with the macronutrients data being way out of sync each day. 

[MjDonley25]

Same issue for me. Come on Fitbit, fix this.

[nibake]

After a bit of troubleshooting, I am have isolated the problem. Whenever the time zone of the fitbit watch disagrees with the phone timezone, the food will log on the previous day. I tend to hop time zones on a daily basis, and I wanted my watch to stay on my acclimated time zone. Unfortunately, due to the calorie logging glitch I have to set my fitbit to sync to the same time zone as the phone in order to properly log calories. It would be great if this glitch would actually be fixed. In the meantime following these instructions will at least allow you to decide if you are willing to compromise on the time zone in order to get use of the calorie counting on the app.

[DietDouger]

Me too.  Just started logging food.  this issue is frustrating!

[TravelerMR]

I have this problem even though I carefully re-sync each time I change time zones.  It’s 1 pm but still my Fitbit is adding today’s food to yesterday.

[joisey77]

Thank you for this. You are absolutely correct. I live near and travel across a time zone several times a week. At least now I know why I've been having issues. It has been so frustrating!! ♥️♥️

[Bbgunz]

I have this issue all the time and it fixes its self randomly.  I find it odd some food I log goes on the correct day and then it starts on the previous day all if a sudden.  I don't know how to fix it. It's been an issue for about a year now off and on.