You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently sets the date as :
date: moment().format('YYYY-MM-DD'),
If the user isn't in the same timezone as the server, this will result in the data getting reset to zero at the wrong time ( from the users perspective ).
It seems to work fine just setting :
date: 'today'
Although I've not tested the rollover yet, this would be Fitbit's problem if it goes wrong...
The text was updated successfully, but these errors were encountered:
I hope to have time in the next few weeks ( need to align with the next-release branch rather than master I guess... I might have some more APIs I can implement for it too, but not sure what is in that branch ).
In the meantime I thought I'd at least share my debugging effort.
On that note, using 'today' seems inconsistent... it seems like it might work AOK for the daily summary object, but doesn't always return the goals object.
Currently sets the date as :
date: moment().format('YYYY-MM-DD'),
If the user isn't in the same timezone as the server, this will result in the data getting reset to zero at the wrong time ( from the users perspective ).
It seems to work fine just setting :
date: 'today'
Although I've not tested the rollover yet, this would be Fitbit's problem if it goes wrong...
The text was updated successfully, but these errors were encountered: