Closed lightmaster closed 6 years ago
Thanks for the nice fixes @lightmaster. The only reason, assuming Fitbit is not at fault, I can imagine for the issue you described is clock drifting between local machine and Fitbit server. If that's the case, we could fix it just as well by waiting just a few seconds instead of 5-10 minutes.
This allows it to successfully retry after hitting the API Limit if there is a small difference between the computer's time and Fitbit's server's time. Also exits nicely if you press Ctrl+c while waiting on the retry.
praveendath92/fitbit-googlefit#21