-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Response 401: Scrobbles unsuccesful #234
Comments
After re-running the auth, you need to restart the scrobbler for the changes to take effect: To anyone else facing
|
Thanks. I had restarted after reauthorizing (and before posting my issue), but it didn’t make a difference. I just now force reauthorized a 2nd time, restarted the scrobbler and all is well!
…On Dec 26, 2022, 7:20 PM -0500, Krut Patel ***@***.***>, wrote:
After revoking and re-running the auth, you need to restart the scrobbler for the changes to take effect: trakts start -r
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hello. I was facing the same issue. My OS is Windows 11. My scribbler was not working since Dec 10, 2022. I revoked access from trakt website then tried to run the command
How should I proceed? |
@anjo-cheenath See #224 Should be fixed in v1.6.1 |
Closing this for now. If someone else is facing this, feel free to reopen. |
Describe the bug
I believe the Trakt API is back online now, but I'm having issues scrobbling. Running
trakts status
returns the following:To troubleshoot, I revoked my TraktScrobbler access from my account at https://trakt.tv/oauth/authorized_applications and successfully ran trakts auth --force
However, my logs show:
I see these messages attached with each episode that I've played recently.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: