nixgates / plugin.video.seren

Repository for Seren Development
319 stars 101 forks source link

[BUG] UNABLE TO AUTHORISE TRAKT #636

Closed thedogzeus closed 3 years ago

thedogzeus commented 3 years ago

Describe the bug Unable to Authorise Trakt

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Authorise Trakt'
  2. Click on 'Trakt Sync Tools'
  3. Scroll down to 'Force a sync with Trakt'
  4. See error 'Seren Error - check log for details'

Expected behavior Have tried every which way to auth Trakt. Trakt auth code popup works and successfully authenticated message appears, but when settings checked, no Trakt account present and any sync or attempt to add account again throws the error. Have dobe fresh Seren install, from a fresh install of the repo and same behaviour. Similar issue prior to update with RD, but that now appears to be OK. Also cannot access provider packages error, throws a 'Seren Error - check log' message.

Screenshots N/A

Kodi Version (please complete the following information):

Additional context

thedogzeus commented 3 years ago

20210622_042051

thedogzeus commented 3 years ago

20210622_042023

thedogzeus commented 3 years ago

20210622_041958

thedogzeus commented 3 years ago

20210622_041930

thedogzeus commented 3 years ago

20210622_041822

thedogzeus commented 3 years ago

20210622_041759

thedogzeus commented 3 years ago

20210622_041708

thedogzeus commented 3 years ago

20210622_041705

thedogzeus commented 3 years ago

20210622_041636

drinfernoo commented 3 years ago

Please attach an actual debug log. These pictures are very hard to work from.

thedogzeus commented 3 years ago

kodi.log

thedogzeus commented 3 years ago

Log attached above ⬆️ #

thedogzeus commented 3 years ago

Now attached. And here it is aswell...incase dl link in thread is flakey

Get Outlook for Androidhttps://aka.ms/AAb9ysg


From: drinfernoo @.> Sent: Tuesday, June 22, 2021 6:43:09 AM To: nixgates/plugin.video.seren @.> Cc: thedogzeus @.>; Author @.> Subject: Re: [nixgates/plugin.video.seren] [BUG] UNABLE TO AUTHORISE TRAKT (#636)

Please attach an actual debug log.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/nixgates/plugin.video.seren/issues/636#issuecomment-865347746, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACO3J6QCR3RU3MF7KXYAIDDTT6TOLANCNFSM47CDQDZQ.

drinfernoo commented 3 years ago

Looks to me like a corrupt database file (or two)... Are you running this in a build? If so, I'd recommend trying it out in a clean install, and if you can reproduce it there as well, then attach a debug log.

JackDinn commented 3 years ago

Iv just installed a brand new kodi 17.1, All was going fine, but seren started failing to update the watchlists from trakt a couple of days ago(ish). I de-authorised it cleaned all the cache etc, rebooted kodi but it will not allow me to authorise trakt again?

Kodi_20210625_185557

The Oath is deauthorizing & pre-authorizing fine? Seren just will not

kodi 19.1 (on shield) seren 2.1.1

log shows 2021-06-25 18:55:19.582 T:14356 ERROR <general>: SEREN (0): Activities Sync Failure: Unable to connect to Trakt or activities called too often 2021-06-25 19:06:57.943 T:15013 ERROR <general>: SEREN (-1): Trakt returned a 429 (Rate Limit Exceeded): while requesting https://api.trakt.tv/oauth/device/code

JackDinn commented 3 years ago

Full log if needed https://pastebin.com/3ZLa4QEH

drinfernoo commented 3 years ago

@thedogzeus For the original issue, it seems pretty clear that there are widespread issues with your install, most likely stemming from an unmaintained and/or faulty community build.

@JackDinn Try again later. That is a different error message, indicating that you are being rate limited due to too many API calls in a short time.

JackDinn commented 3 years ago

Try again later. That is a different error message, indicating that you are being rate limited due to too many API calls in a short time.

I shall do that, thx.

thedogzeus commented 3 years ago

Oky dokes, update; on a clean install of Kodi 19.1 all errors re authentication are cured. However, upon restart of Kodi; Trakt, RD and Premiumize auths are all lost and all custom settings are returned to default (not saved). I will run a few more cycles later to see if its a one off or consistent and post back in due course. Nb. Props to the Dr for the time and energy invested on the project, respect is due 🤘

Chucknorris1975 commented 3 years ago

Oky dokes, update; on a clean install of Kodi 19.1 all errors re authentication are cured. However, upon restart of Kodi; Trakt, RD and Premiumize auths are all lost and all custom settings are returned to default (not saved). I will run a few more cycles later to see if its a one off or consistent and post back in due course. Nb. Props to the Dr for the time and energy invested on the project, respect is due 🤘

Any luck?

thedogzeus commented 3 years ago

No joy on clean vanilla Kodi install or fresh Xenon community build. Both dropped the authorizations after about 30 min. Will shelve this one for now and see how future release(s) go.

drinfernoo commented 3 years ago

Are you allowing the database rebuild to fully complete after authorizing Trakt?

It should give notifications of it's progress along the way, and a final notification indicating that it finished successfully.

thedogzeus commented 3 years ago

Hi Dr, yeah Trakt sync progress is displayed and successfully completes, in both environments. Auth and sync has been performed both with and without VPN and de-auth issue still presents. Co-incidently, during the short period that the authorisations do stick (RD and PM), the scrapers fail to find any links, so Im not 100% confident calls to the providers are actually being successfully completed either. I dunno. Perhaps it could be a quirk in my native Android TV environment that is packaged with my Kogan TV. I'll stay tuned for new releases and try again down the track. I've got plenty of other things to occupy my mind atm, so Kodi time is pretty limited right now anyways 👍

drinfernoo commented 3 years ago

This should be fixed in 2.1.2.