I have multiple devices with Kodi with Scrubs installed on them. I also have beatv installed on each. In the past I had no issue activating trakt on each and use them on each. In the past few weeks, I’ve had to reactivate each trakt instance on each device, and only the last teakt instance I activate remains activated, the others deactivate. So now each time I switch watching from one device to the next I need to acticate on trakt.tv/acticate again. This is becoming very frustrating.
Anyone else experiencing this? Anyone have a resolution for this issue?
When I look in my account it shows that one instance of the app/service is connected, but doesn’t indicate if multiples of the same app are connected. I have never had to check this before so I am unsure if it showed how many instances of a app was connected before.
trakt updated their auth token expiry a little while ago but there’s nothing for you to do really. you’ll need to contact the other app or plugin developers for help with those or to have them update their code for the auth tokens
Yeah this is a dumb change they did which they claim is for better security but it’s much far more of a headache for users that don’t use the apps regularly connected to trakt.
I just noticed that the developer would need to ensure their app handles reauthorization every 24 hours, but the last device I authorize stays activated beyond 24 hours. This may indicate the developer has already implemented the resync code necessary for reauthorization.
If the fix is already coded, what else could cause the previous device dropping authorization after a new device is authorized?
if you log in say every 24 hours, the token refreshes, and won’t require you to re-auth. If you say haven’t logged in for weeks, on your other devices or created a backup, both will have a higher chance of having an older api token, and hence expire requiring re-auth.
if the 3rd party app, syncs the token across devices, then it will have a better chance of not expiring. Kodi is one app which i don’t think it can sync across devices real time hence you have to create backups when you make changes.
No, that isn’t how auth works. There is a secondary refresh token with a longer expiration the app uses to get the main token automatically. If the app isn’t doing that, it means they haven’t coded auth correctly.
