OAuth Token invalid every reboot / after a while / no 1440P content

[xxyZIZyxx]

• Add-on Version: 3.0.3
• Kodi Version: 21.2-Omega (Amlogic-ng.arm)
• Kodi GUI Language: english
• Operating System: coreelec
• Operating System Language: english

I followed the new written wiki, and tried several alterations of it over the course of last few days.
Following the guide step by step, the addon seemingly works afterwards.
BUT everything implodes after a reboot of the machine or watching for an hour or two. It complains about not being able to renew the token.
Also the highest resolution provided is 1080P.
As said after a while or reboot the Token is invalid, also the inserted maintenance OAuth Token has vanished then or at least isnt shown anymore in the plugin.

Since Forum is dead (never got an answer in over a year) I figured I'd open a bug here, asking for help.

So far I'm back to 3.0.2 provided by coreelec repo, since this is working and survives reboots.

I followed those steps

1. Settings - Login - Login (device code)

2. Visited twitch.tv/activate and followed the steps

3. Registered an application at dev.twitch.tv/console/apps chose type to be public and inserted the http://localhost there too.

4. Entered the Client ID in Settings - Developer - OAuth Client ID

5. Loged in again via Settings - Login - Login (device code)

6. Settings - Subscriber and Turbo Benefits - Login: ad-free playback / Turbo (device code) and authorized

Shouldn't the OAuth Tokens for Login, Turbo and Maintenance be shown after everything was done? Those fields appear empty in every try I had so far. Even when addon works for now (without 1440P resolution though).

[einanderson]

Your steps 1–6 match the README, so the setup is fine. Two of the three symptoms have a known cause.

No 1440p: two things have to line up and neither does on your setup. Settings - General - Supported codecs defaults to Twitch default and has to be set to H.265 (HEVC) (that is missing from the README, sorry). And the library script.module.python.twitch has to be 3.0.3 — the plugin silently drops the codec request with older libraries so it stays compatible. 3.0.3 of the library only exists as a GitHub release and has not been submitted to the Kodi repo yet, so CoreELEC ships 3.0.2 and the setting cannot take effect. Note that 1440p only exists on Enhanced Broadcasting channels anyway.

Empty token fields: expected. Since 3.0.3 the tokens live in userdata/addon_data/plugin.video.twitch/oauth_tokens.json; the settings field is only a legacy mirror that the settings dialog can overwrite. It does not mean the login failed.

Token going invalid: that is the real issue and I need your kodi.log (or at least every line containing OAuth). Two very different causes look similar from the outside: missing client secret means your own Client ID is not being used, Invalid refresh token means the rotated token is not being persisted. Please also check whether that JSON file exists and whether its timestamp changes.

For context: the login and codec code in 3.0.3 was only tested on Kodi 21 with LibreELEC on a Raspberry Pi 4 — CoreELEC on Amlogic has not been tested at all.

[xxyZIZyxx]

Ty for clarification, appreciated!

I set the Supported Codec Field to H.265 but ofc, did not fetch the newer python.twitch plugin.
I will check if files exist and retry 3.0.3 with newer python module for sure - might take a while, but will answer here.

If problems persist will issue logs!

Since empty token fields are to be expected:
Is it possible to still issue a checkmark or something similar for "there was something inserted and this site does not need to be touched?" - or read the token given in the file and give the last 3 digits of it?

As said I redid the config so often... sometimes I was not sure if I already logged in or not this try, without a sanity check I always wasnt 100% sure... .

[xxyZIZyxx]

I uninstallted Twitch 3.0.2.
Installed Twitch 3.0.3 and updated python. twitch module from 3.0.2 to 3.0.3.

After this I followed the wiki, set HEVC Quality, too and only 1080P content?
(Made sure Inputstream adaptive is set to adaptive, twitch is set to adaptive)
Rebooted.

Go into following channels--> Channels get listed including thumbnails and message appears:

"Client id mismatch
Press OK to resolve"

Then trying to play one of the listed chanels, the following message appears:
"An OAuth Token is required for access, go to 'Settings' - 'Login' - 'Login (device code)' to generate one"

Followed by:
"One or more items failed to play. Check the log for more information about this message."

I did not recreate a token, I just selected the channel again and it worked, including 1440P H265 =).

Then I rebooted, no error messages shown, but back to 1080P again.
When I select a channel to play, and via contectmenu select quality "Source". A stream starts with 1440P Content again for like 5 seconds and ends again.

Since H.265 is bound to Turbo, I went into settings again and redid the turbo subscription.
Now I pressed play again and video was in 1440P H.265 again.

Stopped stream, pressed play again and video was in 1080P H.264 again.
Stopped stream, pressed play again and video was in 1440P H.265 again.
Stopped stream, pressed play again and video was in 1080P H.264 again.
Stopped stream, pressed play again and video was in 1080P H.264 again.
Stopped stream, pressed play again and video was in 1080P H.264 again.
Stopped stream, pressed play again and video was in 1440P H.265 again.

I dont get it.

I rebooted several times, seemingly all tokens work / at least no errormessages -for now, will report if anything changes again- but if a channel plays in 1080P or 1440P is random.

Then I went ahead and copied kodi.log and kodi.old.log only to discover... debug logging disabled.
I will redo the whole thing, but since this took me like 2 hours already, I figured I'd add this here.

Will report back, dont know If I have time (and allowance ;)) to do this in the next days, but will report back, promised!

[xxyZIZyxx]

Came home a few minutes ago and decided to watch a stream.
Fired up coreelec, selected a stream --> 1080P. stopped playback, restarted it --> 1440p Fine.
Leaned back when a message appeared in lower right corner and disappeared.

Checked kodi.log (still no debug, sorry):

2026-08-07 20:35:18.448 T:4140 warning : Twitch: OAuth: refresh needs a public client id (this one is confidential); set your own under Settings > Login. Falling back to manual login.
2026-08-07 20:37:01.852 T:4277 warning : Twitch: OAuth: refresh needs a public client id (this one is confidential); set your own under Settings > Login. Falling back to manual login.

Guess I'll go to settings login again and login?

Working for now:

2026-08-07 21:21:11.866 T:9072 info : Twitch: OAuth: device login succeeded, refresh token stored

Regarding the strange "jumping Quality", as I understand the automatic mechanism in inputstream adaptive might be the culprit.
My connection provides roughly 300MBit/s down and ~50 up, should be plenty. Will play with its settings and report.

[xxyZIZyxx]

I got two debug logs.

One is ~250 Megabytes and shows the installation, including login and watching some streams - mostly in 1440P -.
(I still dont get why sometimes Streams only play in 1080P and need to be restarted two or three times to finally switch to 1440P).

One is ~160kilobytes where I fired up the mediacenter the next day and I could not use Twitch again, cause of message:
"2026-08-10 17:46:48.772 T:4152 debug <CAddonSettings[0@plugin.video.twitch]>: trying to load setting definitions from old format...
2026-08-10 17:46:48.778 T:4152 warning : Twitch: OAuth: refresh needs a public client id (this one is confidential); set your own under Settings > Login. Falling back to manual login."

After this I saved the logs and disabled debugging.

Then I went to Settings - Login - Login (device code) and proceeded into watching streams in sometimes 1440P.
After roughly an hour same message as above appeared and I had to relogin again.
Today I had to relogin again.

Do you want me to zip those logs and send them?
Since there might be sensitive data in them and the big log exceeds 1000k lines, I do not want to publish this in the internet.
Or what information do you want me to provide and make public out of those logs?
e.g. I can "grep -i something -B10 -A10 > /debug.log" through the files, but what should I look for?

[einanderson]

Thanks for sticking with this — you found a real bug, and it is ours, not your setup.

Why your Client ID keeps dying

Please check Settings - Developer - OAuth Client ID. I expect it to be empty,
even though you entered it.

The add-on wipes it itself. valid_token() compares the Client ID your token was
issued for with the Client ID you have configured. If they differ and the token
belongs to the bundled Client ID, the add-on clears your setting and falls back to the
bundled one — and the bundled one is confidential, so it can never refresh. That is the
exact warning you are seeing.

Following the README puts you straight into it:

1. README step 1: log in via device code → the token belongs to the bundled Client ID
2. README step 2: register your own app, enter its Client ID
3. next API call (browsing, or the background service) → mismatch → the dialog you
   reported, "Client id mismatch / Press OK to resolve" → your Client ID is cleared
4. README step 3 "log in again" → uses the bundled Client ID again → token cannot be
   refreshed → dies about an hour later

Every repair attempt in that order triggers the same wipe, which is why it keeps coming
back day after day.

If you want to confirm it in the logs you already have, this one line is enough — no
need to upload anything:

grep -n "OAuth Client-ID mismatch" kodi.log

Workaround, no new build needed

The trick is to have no token present while you enter the Client ID, so the check
never runs:

1. Settings - Login - Revoke token (or, with Kodi closed, delete
   userdata/addon_data/plugin.video.twitch/oauth_tokens.json)
2. Then enter your Client ID in Settings - Developer - OAuth Client ID
3. Then log in once via Settings - Login - Login (device code)

Now the token belongs to your own Client ID, the check passes, and the automatic refresh
works. The ad-free/Turbo login is separate and unaffected.

Fix

A patch is prepared: the add-on no longer clears the configured Client ID — it discards
the stale token and asks for a new login instead. The README will also put the Client ID
step before the login so nobody walks into this again.

The 1080p / 1440p lottery

That is a different problem, and it is not InputStream Adaptive's bitrate adaptation —
your 300 Mbit/s are not the issue.

Twitch mixes one HEVC variant into the H.264 ladder of the same master playlist.
ISA turns that into two video adaptation sets (one per codec), both flagged DEFAULT,
and Twitch shuffles the order of the variants on every request. Kodi picks by
remembered per-file stream index / manifest order, so each start is a coin flip between
the H.264 1080p branch and the HEVC 1440p branch. Exactly the pattern you describe.

You can switch it by hand while the stream is running:

• Open the OSD → Video settings → Video stream. There are two entries (H.264 and
  HEVC); the HEVC one is the 1440p branch. They are labelled by codec, not by resolution.
• Caveat: switching the video codec mid-stream often ends in a black screen — that is
  your "1440p for about 5 seconds, then it ends". Switching the audio track once first
  forces a demuxer reset and makes the codec switch survive in my testing.
• Kodi remembers the stream index, not the codec, so this does not reliably stick across
  restarts while Twitch keeps shuffling the order.

Solving it properly requires rewriting the master playlist before handing it to ISA
(single audio track, HEVC-only when an HEVC variant exists). That is not in 3.0.3.

[xxyZIZyxx]

Thank you for your extensive explanation :) Appreciated!
I did not realize how often I tune into twitch for just a few minutes on my mediacenter - the plugin just worked the last years... now with the new version, I had to redo the token 2 or three times yesterday night - while being accustomed to renew one or two by hand every few weeks on older version.

Thank you and your colleagues for keeping this alive!

Regarding the grep -n "OAuth Client-ID mismatch" kodi.log part, I wasn't able to find any appearance of this in the two debug logs.

I'm going to test this soon and will let you know the outcome.

[xxyZIZyxx]

As promised my findings:

Your new steps worked.
At first I also revoked Turbo Subscription, too and was greeted the next day with same problem.
So I redid word for word, did not touch Turbo again, and working!
Usually I had to relogin every few hours, now I'm back to old behaviour, it just works without any complaints regarding the tokens!

Also your advice for switching streams is worth every letter in gold!
The blackscreen issue you mentioned, seemingly only happens when audio isn't working too.
But since I'm used to this, I usually change audio stream first, when audio plays I switch to 1440p video stream and this switch always works (so far).

Thank you, for keeping up with my rambles here and all your advice.
And ofc also for keeping this plugin alive and working!