Trakt: check if refresh token lifetime is too short, report it to them

[UweTrottmann]

There are multiple reports from users that indicate they now need to frequently sign back into their Trakt accounts. This might indicate that either the refresh token is not getting stored or the refresh token lifetime is way too short.

As for the lifetime, can check that myself. Also check the OAuth spec on the recommended lifetime. I remember it should/may be multiple times the lifetime of the access token. Update: can actually not check, only the validity of the access token is returned. How long a refresh token is valid is totally up to the authentication server.

So for both issues, need to wait on users sending debug log files.

[UweTrottmann]

Based on #1126 I checked logs of error reports of TraktCredentials.refreshAccessToken failing. And it appears there is sometimes an initial successful request with a 200 HTTP status code, but with no new access token returned (log is ERROR/TraktCredentials: refreshAccessToken: returned data not valid). Which might indicate there is indeed a captcha page being shown.

Created a discussion on the trakt-api project about this.

[UweTrottmann]

The trakt-api discussion was closed as "outdated" (by a bot, however). So have another look at the error logs.