iamkroot/trakt-scrobbler

[BUG] Response 401: Scrobbles unsuccesful

brijazz opened this issue · 5 comments

Describe the bug

I believe the Trakt API is back online now, but I'm having issues scrobbling. Running trakts status returns the following:

The scrobbler is running
Monitored players: plex
No activity yet.

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:

2022-12-22 06:47:39,054 - DEBUG - scrobbler - utils - Response: <Response [401]>
2022-12-22 06:47:39,054 - WARNING - scrobbler - scrobbler - Scrobble unsuccessful. Discarding it.

I see these messages attached with each episode that I've played recently.

Desktop (please complete the following information):

  • Mac OS X 10.13.6
  • Python 3.9.12
  • Plex for Apple TV / Plex Web

After re-running the auth, you need to restart the scrobbler for the changes to take effect: trakts start -r

To anyone else facing Response [401], run these steps:

  1. trakts auth --force to get a new API key
  2. trakts start --restart to restart the app
  3. (Optional) trakts backlog clear to send the scrobbles from downtime.

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 trakts auth --force however, I got the following response

OSError

  [WinError -2147024809] The parameter is incorrect
  at .local\pipx\venvs\trakt-scrobbler\lib\site-packages\desktop_notifier\winrt.py:75 in __init__
       71│     ) -> None:
       72│         super().__init__(app_name, app_icon, notification_limit)
       73│         self._appid = CoreApplication.get_id()
       74│         self.manager = ToastNotificationManager.get_default()
    →  75│         self.notifier = self.manager.create_toast_notifier(self._appid)
       76│
       77│     async def request_authorisation(self) -> bool:
       78│
       79│         Request authorisation to send notifications.

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.