-
Notifications
You must be signed in to change notification settings - Fork 79
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
error playing live streams/vods #461
Comments
I started getting an identical problem just now also. Streams appear, but error out on attempting to play.
|
I'm having the same issue
|
Can confirm, observing same issue as above. Although I was trying to watch a VOD rather than livestream.
|
Streamlink is having the same issue: streamlink/streamlink#2680 |
Enabling debug logging gives some insight:
So it seems like the used API call is not available like this anymore. |
Anyone know of a workaround? |
I managed to get it working by changing the Lets hope this isn't Twitch shutting down 3rd party applications :( |
I had to remove my existing auth-token, then change the client ID to the twitch website one, then pull the new auth-token from the website manually (not use the built in request-auth-token function). If I did not remove my existing auth token the change in the client ID would be rejected (probably because the token was associated with the v3 api?) To me it looks like client IDs and tokens associated with the v3 api are what are not working. |
Neither of the above worked for me, but I might have used the wrong token. That being said even if I have no auth info at all trying to play a stream is erroring for me. |
Seeing the same error here. Hopefully this isn't the end of the v3 api. |
Its working again. |
Working again here. With the client-id empty. Just using the 0authtoken. Generated by twitchaddon.page/***** link. EDIT: And broken again? |
I was getting the same API fail and/or timeout issues when Twitch tied itself in knots dealing with the huge extra load from the Fortnite new season event a few weeks ago. |
"following live channels" work again, without manipulation with token :) |
Problem back today again. Seems that there's not much to be done other than hope Twitch doesn't break the undocumented API endpoint permanently. From the discussion over at streamlink it seems there's no real alternative. Question is would it be possible to use the Twitch client ID with your web user auth-token and still get Followed channels and similar in Twitch-on-Kodi? |
yes problem back again today :( |
Confirmed, same problem is back. I hope this is fixable... |
I just streamed something using the 'fix' mentioned previously (their client-id, my auth token). |
Indeed, I can confirm this is works though is not the ideal solution. Credit goes to @fragande for detailed instructions |
Yeah, it's a workaround for now I guess. Today when I changed back to the Twitch client ID + web auth token I actually didn't lose Followed channels, no idea why. According to the cookie data the web auth token should be good for 6 months. If it's possible to keep Followed channels and such it could be a "permanent" solution (until Twitch shuts that down too ...), albeit a very dirty one that probably breaks ToS. Third party apps are supposed to use their own client ID's.
Did either of you get to keep Followed channels when doing this? |
Surprisingly enough yes, the followed channels do work as expected |
this issue seems to be wide spread across several 3 party viewing 'apps' . Streamview Is also experiencing this as well |
I guess I did something differently the first time then. In theory I don't think there should be a difference as it's the same data Twitch-on-Kodi is authorized to access when creating the OAuth, but didn't work for me first time around.
Yes, it's affecting every 3rd party app using this API endpoint. Seems Twitch are periodically blocking every client ID but their own for unknown reasons. It seems Twitch aren't happy about this endpoint being used in the first place as it's undocumented and unsupported but they haven't cracked down on the usage of it until now AFAIK. |
I noticed a few versions of the Twitch API in the developer section of their site. I don't know much about this, or other addons, but how difficult would it be to use a newer more supported API version? I get there would be work involved but would it be worth it for hopefully some future proofing? |
Can anyone explain the fix workaround? When i use twitch id oauthtoken (kimne78kx3ncx6brgo4mv6wki5h1ko)and the web generated auth token ,its still not working? |
As mentioned, this is due to an undocumented API endpoint and is not included on their developer site. We are currently use v5 at the moment for all other functions, which currently has no eol date. The helix API is ready in the module for when the time comes, it comes with additional limitations which is why we haven't migrated to helix yet. Currently the only way to temporarily workaround this is to use the client id and oauth token from the website. |
@xenius |
you want to use the oauth token you see in the same place as you found the client id, not the one you generated from the add-on (back that one up first). |
Where can i find the exact 2 things i need to get this working again? |
True, maybe a toggle in Developer settings, Disable Playback Authentication (Workaround) |
Actually working on something atm. There you can put in the web pages client id and oauth token(for users who want subscriber only content access), they will only be used on those end points. So regular auth credentials can be left in place, and if Twitch happens to revert the change users can just delete the private credentials. |
The new zips are ready, https://github.com/MrSprigster/Twitch-on-Kodi/releases/tag/2.4.7 If you've already changed your client id and/or oauth token, you can safely remove the client id and use your old oauth token. If you have the oauth token from the web page, you can add that to If the client id changes from You can also edit the
|
I updated the previous comment with new zips, 2.4.7 and 2.0.10. Following Games, Toggle Follow on Games started responding with the |
Yeah it works again! Thanks! |
I updated one of my Kodis yesterday. Thanks for the hard and fast work. I wonder if I'm the only one having issues accessing the "Game" menu? I can see the featured streams but not the Games section. I cannot provides logs at this time. I'll investigate this evening or tomorrow. |
@efirshik it is case sensitive https://twitchaddon.page.link/eetJ |
I think i need some help. On my Smart-TV with Kodi installed it doesnt work at all since Twitch changed the API or whatever. When i enter my OAtuth Token, he shows me the correct Channels i follow, but when i click a Stream to watch there is a popup with "Gone [410] This API has been removed." And later he say me: Invalid OAutch Token. |
@Dr0plexx you can read @anxdpanic comments above.
|
Thanks, but i installed them already. Those Errors are "made" with the Pyton 2.0.10 and Kodi 2.4.7. |
Oh, sorry :/ |
Would need complete logs with debug logging enabled to see what is going on. It is and has been working with all features for me. |
Thats the problem. I dont know how and where to find those loggings on TV. Maybe its impossible to reach those files because of very limited access and the lack of a File Browser or something like that. |
Yes it would be different every time, you're generating a new one every time that is done. https://kodi.wiki/view/Log_file/Easy <- Follow this, and use step 3.1 for uploading the log |
Thats nice. Here it is: |
That's just a regular log, need to do Step 2 first |
Sorry. |
That was the one. Looks like it is using the wrong Client ID Can you double check that Also |
Wow that kimne.. Client ID thing was the only Problem? It works now with my OAuth Token i created in the first row and the kimne.. ID in the Private API. I have tried that some days ago. But maybe in the wrong row. I am sorry for my dumbness :) |
Hmm. Updated Python script, updated the addon. Now I dont get an error, but the stream starts loading for a long time then i get "One or more items failed to play". Tried unisntalling and reinstalling from scratch, but got the same issue. Clientid is correct. Also tried with and without my oauth token. Is it only me? |
2.4.7 was merged into the official repository, will be available when caching allows |
For others who might run into the same issue as me. I ended up having to change the clientid as well, because streams I subscribe to (so I can watch their past broadcasts) stopped working for me. To get the new clientid, I used firefox as above and copy and pasted the contents of the |
The text was updated successfully, but these errors were encountered: