11-29-2020 02:24 - edited 02-21-2021 01:38
11-29-2020 02:24 - edited 02-21-2021 01:38
So my Inspire HR has been great up until I moved to Brazil from the US. Now my app consistently shows the correct date and time on everything (inc. the tracker) except the log screens which are a day behind the current day. On the food log I am required to log my current day by pressing on the next day! On the water log I am unable to tap the current day so I haven't logged water for weeks. I tried a number of things like reinstalling the app, confirming my timezone is correct everywhere, confirm my location is correct in the app and the phone, reboot the device and calling support who I recall resyncd my account to the server but not sure. It didn't fix the issue. Everthing else works normally. I use a vpn located in brazil or the usa and my timezone is -3 gmt. I am guessing my personal database logs have gotten corrupted on the fitbit server(s). Any solutions before I wipe 11 months of goal achieving and weight loss by starting a new account?
Answered! Go to the Best Answer.
02-20-2021 15:01 - edited 02-20-2021 15:58
02-20-2021 15:01 - edited 02-20-2021 15:58
Sadly(or happily since my Fitbit is normal again) two months later I answered my own issue, partly, since I am only able to work around the problem. I believe this is a app bug. I first determine that no matter if I use in the app automatic time and/or automatic location the Food and Water log uses the system time of my phone. I am in Brazil -3gmt
. If I set my system time to SaoPaulo/Brasilia (my location) in either manual or auto mode, the Fitbit App shows the error I posted about. Strangely if I set system timezone to Argentina(Buenos Aires) or other zones in the same timezone as Brazil or zones nearby, the app has today's date defaulting and applying correctly in both logs appropriately. In addition to this weirdness, I found two authorized devices (under "app settings" in Fitbit app) for my same phone for which I deleted one located in Brazil and that seemed to help the time. I suspect this may be a artifact of using a VPN through more than one country on different occasions. I am not sure which caused the errors but at least I know now what to look out for. The only way to test my fix is to try logging at midnight and see what today's date the log defaults too. I am using Fitbit app v3.37.1 in an Android. I hope this helps other users. Do the Fitbit developers even bother to read these issues?
02-20-2021 15:01 - edited 02-20-2021 15:58
02-20-2021 15:01 - edited 02-20-2021 15:58
Sadly(or happily since my Fitbit is normal again) two months later I answered my own issue, partly, since I am only able to work around the problem. I believe this is a app bug. I first determine that no matter if I use in the app automatic time and/or automatic location the Food and Water log uses the system time of my phone. I am in Brazil -3gmt
. If I set my system time to SaoPaulo/Brasilia (my location) in either manual or auto mode, the Fitbit App shows the error I posted about. Strangely if I set system timezone to Argentina(Buenos Aires) or other zones in the same timezone as Brazil or zones nearby, the app has today's date defaulting and applying correctly in both logs appropriately. In addition to this weirdness, I found two authorized devices (under "app settings" in Fitbit app) for my same phone for which I deleted one located in Brazil and that seemed to help the time. I suspect this may be a artifact of using a VPN through more than one country on different occasions. I am not sure which caused the errors but at least I know now what to look out for. The only way to test my fix is to try logging at midnight and see what today's date the log defaults too. I am using Fitbit app v3.37.1 in an Android. I hope this helps other users. Do the Fitbit developers even bother to read these issues?