Open wscourge opened 1 year ago
same issue
To circumvent this issue, I propose we reuse login information by utilizing GCClient.loadTokenByFile('/path/to/save/tokens') or GCClient.loadToken(oauth1, oauth2);. This approach should help us avoid unnecessary logins and the subsequent triggering of Garmin's security policy
It happened for multiple requests on multiple accounts. The problem is that when password reset is requested, Garmin sets up a temporary password and does not allow logging-in with the old one.
As mentioned, multiple requests with multiple accounts, and this does not happen always, but sometimes it does. I wonder if the requests frequency might have something to do with it? I send them every few minutes (5-10).