-
Notifications
You must be signed in to change notification settings - Fork 111
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
Video's don't play with "content not available on this app" error #442
Comments
Experiencing the same problem. It started yesterday, April 12, with some channels but as of now it wont play anything anymore. Add-on version: 6.8.25+matrix.1 |
I have exactly the same issue since today: Add-on Version: 7.0.1 |
I experienced the same issue yesterday evening, but repeatedly retrying the same video would often result in a successfully played video. By the end of the night, no amount of retries would result in playing any videos. All videos played fine in a browser. |
I think that YouTube changed something.
El jue, 13 abr 2023 a las 16:06, ThubLives ***@***.***>)
escribió:
… I experienced the same issue yesterday evening, but repeatedly retrying
the same video would often result in a successfully played video. By the
end of the night, no amount of retries would result in playing any videos.
All videos played fine in a browser.
—
Reply to this email directly, view it on GitHub
<#442 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4KDOK3ZFMDMGVFNWRSFXDTXBAB5FANCNFSM6AAAAAAW4VEH2A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
North America, broken @ 0730 EDT across 4 devices, all using same account. Attempting to reauthorize API, at 2nd OAuth token input, receive this from google.com/device: "Access blocked: Project xxxx has not completed the Google verification process" |
Kodi 20.1 (LibreELEC 11.01) Same issue. I still appear to be logged in as it loads my subscriptions but when I go to play them it says that the content isn't available on the app. |
On 1 of 4 devices that failed I did the following: I then went back into the project on console.cloud.google.com and added this 2nd account as a test user and re-did the OAuth tokens.
I was then able to successfully view. Update: Adding a test user to an existing accounts projects OAuth and logging out / logging back in to renew the OAuth tokens does NOT seem to resolve the issue but I need to do more testing. The newly created account however was able to view on a device that was not working this morning. Update2: This 2nd account setup workaround now fails with the same error message. |
Same here Spec: part of log: |
Same issue. |
I believe this was intentional on Google's part, though perhaps not specifically targeting this plugin: This same error message has effectively killed off the last version of the Vanced YouTube client for Android. |
Just to give some update from other place (CE). I had exactly the same symptoms yesterday, but today I was able to flawlessly play two Videos from YT. So it seems that it was kind of a transient problem on the YT part. |
@bartosz-antosik based on your comment, I have tested here again this morning: We are still seeing the same issue. I have tried the following:
So it does not matter whether you use HD or SD settings, nor which prefered codec you've selected (in InputStream). Interesting observation: We have another mediacenter running LibreELEC 9.2.8 (Kodi 18.9) and the latest Python2 version of the Youtube Plugin. This old version currently is still able to play video's normally. |
Has anyone tried to replace the user agent string in this plugin with a more recent version? Its possible youtube deprecated ancient devices and browsers for playback and takes the http requests for coming from one of those. |
@Fludizz I understand. Cannot really tell why is this. I got here yesterday, following "content not available on this app" prompt which described precisely my situation which started in the evening the day before yesterday. So I am only describing my situation, the generalization I have made might have been premature. On the other hand, it may be some rolling update to the servers' functionality, etc. So generally it seems to have reverted to working for me. |
Well it does not seem to be that simple just to change the user agent, but I dont understand the code well. Considering the exception raises in |
Same here. Seems to me that Youtube is systematically blocking access to apps that don't show ads. Hopefully there is a workaround or compromise. |
Solved (for me):
I still don't know what the consequences of unchecking this option are, but now all videos work fine! Kodi 20.1 |
@Rferreira2k Cant confirm that, still fails at the same location with the same error.
|
Still failing with and without Force SSL Certificate Verification setting. Reconfiguring using a Google account that has not watched videos within the last 6-9 months, I was able to get them to play on RPi3b+ and Vero4k+. At least, for the moment... (Force SSL cert verification setting does not appear to have an effect with the new user account.) This requires resetting a new API key, client ID, secret as well as the 2 OAuth keys. And it may not work for very long. -- You'll also need to re-add any channel subscriptions as well so it can be a bit of a pain. And again, I'm not certain how long this workaround (if it works for you) will continue to work. (Vaguely reminiscent of DTV's Black Sunday??) YouTube Addon: 6.8.25+matrix.1 Update: Still working after 24 hrs. |
Video's don't play with "content not available on this app" error |
Same Issue here. |
Possibly this might work as a quick and dirty workaround (while waiting for a proper fix)? Possibly a proper fix could be made using https://github.com/lekma/script.module.yt-dlp/? |
It was fixed for me 14 & 15 April, but today it stopped again. This is on LibreELEC 10.0.4 (RPi4.arm). |
For me it was not working the last two days but today it is working again. Kinda random. |
Doesn't work with the same error. KODI 19.5 |
Video's don't play with the "content not available on this app" error
|
I've been seeing this error intermittently for the past few weeks. Does it still happen if you're subscribed to YouTube Red? |
Tried again yesterday evening, April 16, and I was able to play a video again! However, today its not. I guess its clearly not a bug but rather Google who implemented an allowe/dissallow switch for third party apps. |
There is a path forward which would fix it. You pretty much describe it at #442 (comment) The main annoying part is:
The settings file format changes along with the migration to Python 3. With Python 3 set back to 2, and that settings file hand modified back while retaining tweaks.
At which point you'd probably be a happier and less stressed person in general. |
I really don't know what you are trying to achieve by misunderstanding and incorrectly explaining my own comments back to me, but it is quite amusing, so keep going mate. FYI there is no Python 3 specific code being used, and you are still mixing up the Leia and Matrix branches, so maybe you can have a look at that part first for your next act. |
That's right. That's one of the many reasons why updating to Python 3 during patching was a mistake. Lets make this very simple. Is updating a major version in dependency something which is done during a patch version release? Can you think of any reasons why this should be avoided? |
Lol... I really don't know why you want to keep going at this.
There was no update to Python 3 code, it is the exact same code.
Major version of what?
Avoid what? Are you now tilting at the windmill called xbmc.python? That is provided by Kodi itself, not by the plugin. Different versions of the plugin target different Kodi versions using different branches. This has been explained to you multiple times. Different features and updates were added to the Matrix and Nexus branches of this plugin, and not to Leia, because Leia was no longer supported. Even though you yourself could not manage to do so, multiple people have already done the work to bring those additional changes to the Leia and Matrix branches as well - it is not that difficult but does require time and effort. Despite how much you complain about not being able to to do this yourself, all you are doing is making yourself look extremely ignorant. Are you really so naive to think that if you can't do something that it must be impossible? That the principles of semver have been violated (!!) and that's why you can't seem to understand what is going on? Let's just conveniently ignore those other people who have already achieved the impossible shall we? |
Python. This commit was mixed in with the patch rather than having the fix separate to major dependency updates.
You having to rage daily when people point out that the software no longer works for them. By keeping Major version updates of dependencies out of Patch versions you avoid the difficultly now being experiencing in backporting those patches.
We can do without the ad hominem nonsense and toxicity thanks. I have a functional build from source, I'm more concerned about the people unable to do this for themselves and who rely on repo releases. |
@mryellow - You are so utterly confused, but if you just took the time to understand the situation and read the explanations given to you, instead of complaining about nothing, you just might be able to get there in the end.
Lol so you are complaining about It is not mixed in with anything. It was a new commit in the the Matrix specific branch that targets, wait for it... Kodi Matrix. The plugin does not bump this arbitrarily, the version of Kodi version being targeted does.
This "Major version updates of dependencies" is a single line in a single file, if you think this is so critical, you can just change it back and everything should just magically work because of the magic of semver right? There is no difficulty, despite your complaints. Everything is in seperate branches. You just don't know what you are talking about and continue to mix up Kodi Leia, Matrix, and Nexus and the associated branches for this plugin, that individually targets those different Kodi versions. Here is an example that may blow your mind: #496 Funy how you seem to be the only one having problems in understanding how this all works.
That is cute. Was all of the following from someone else?
To be clear we all know the current release of this plugin does not work (thats what this issue and others are for), but you are the only one complaining that the entire project is an unmaintainable mess because you can't figure out how to create any backport fixes. The only personal attacks are coming from you - you literally do not know what you are talking about but still want to argue about how to develop this plugin and insult and condescend to anyone who has attempted to explain to you why you are mistaken. You have also continuously implied that:
If you weren't so earnest in explaining how you know better than everyone else, and denigrating them for your own inability to understand how different branches work and how to create backport fixes yourself, I would normally just consider you a run of the mill internet troll, but I think you actually are just this insufferable. |
@MoojMidge what is support policy for that plugin? From what you said, Matrix sitll gets support right? So we can expect updates to be pushed to official repo? |
I'm complaining about
It breaks Matrix on some platforms. There are related changes in
You are mistaken. Please just stop with the toxic vitriol. |
Yes I know, but just because you say something doesn't make it true. The change happened in a completely different branch for a completely different version of Kodi. Why is this so difficult for you to understand? Your basic premise has been wrong from the very start but you can't seem to give up this fixation (how many months has it been now?)
No it does not. You may be confused because you are not very familiar with how all this works, but a Matrix release of this plugin will be compatible with Kodi Matrix for all platforms.
No there are not, this has nothing to do with Python 2 vs Python 3. You may be confusing the two issues because you don't know what those commits actually do, but in fact the Matrix specific changes for the settings may actually be compatible with Kodi Leia - it just hasn't been tested. Why don't you do something productive, give it a go, and report any problems? All that has happened is that new updates were made to a branch that targeted the current Kodi branch at the time, and no similar updates were made to the old branch because it was not supported. If you want to support it you need to make similar Kodi Leia changes to the correct branch, as has already been done in #496 and a bunch of previous PRs that you continue to ignore.
Nope. I'm very certain I know what I am talking about. The "
You are in control of yourself. I'm simply pointing out that you are mistaken and you continue to be mistaken while you go around insulting people who aren't just pretending to have knowledge of the topic you are arguing about. You can take these responses however you want, but you are a random person on the internet and have no say in what I say or do. At every step in our discourse I have afforded you the same level of respect you are providing everyone else. A normal person with some perspective and the ability for introspection, upon having troubles figuring things out, would have asked for some help. Instead we have you, who goes off blindly blaming everyone else for being an idiot, because you just don't understand what you are talking about and refuse to listen. |
@MoojMidge |
Rather than engaging with this I'll simply repeat what I said earlier. It's all good mate. |
I totally agree. You are doing an amazing job keeping this plugin working properly for us end users ,I am very grateful for all your hard work and dedication @MoojMidge , Using Omega ,Windows 11 , AH2 |
@MoojMidge thank you for your dedicated hard work on this plugin and doing your best maintening it. I guess it’s time to close this issue even if some people are unhappy with it. I also want to see the last version as soon as possible on the Kodi addon repository - but time is precious and some time you just do not want to do it just because and you do not have to justify it. Noting that the temporary bypass should be at the hand of most people reading this issue on Github (downloading manually the last version and extracting it in the right folder - taking care to backup the current installed version by copying the directory somewhere else). If people are unhappy and think they can do better - I guess they can easily fork the addon and propose a «better» version on their own time. Cheers |
Or just dump the whole project, as this is a mandatory failure (FYI the plugin is NOT WORKING since this year april.) |
Just in case someone is still wondering how to (potentially) fix this and feels lost in this 600 comments thread like I did:
|
It is working for me. Thank you guys @MoojMidge @Chaphasilor ! |
Thanks to (mostly) everyone for the patience and understanding, as well as the valued contributions of those who have taken the time to provide guidance and explanations to help others. A new final release has been published to fix this and other issues: v7.0.2.1 It will soon also make its way into the official Kodi plugin repository, to provide an automatic update for those who are unable to install the release manually. Note that the Matrix and unofficial versions have not been tested. You can report any problems with these in a new issue report. With this release out of the way, I think this issue can now be closed 😃 |
What about |
There are already PRs for Kodi Leia that have been merged, two currently still open, and others to come if people decide to continue support. This won't include me, although I may try to update the workflows to submit a release to the official Kodi repository (but this would be a fairly low priority). This has nothing to do with Python 2 or Python 3 support and there is no reason to create a random v6.9.x release when the master branch is already using v7.x Would prefer not to get into this again, the situation has been explained in great detail already, and nothing has changed. |
Is this issue fixed by the release v7.0.2.2 ? |
Yes, v7.0.2.2 includes a fix for this |
For those who run into it, same as me, even having v7.0.2/whatever. |
I am getting this out of the blue on 7.0.4-nexus.1 |
same |
same. |
Same problem on Eminent EM7680 box. |
No one is having this same problem now. This issue is about a specific error message that appeared resulting in no video playback, and has already been resolved over 5 months ago. You may be having a different issue where the wrong video plays - a short 5 minute video which shows |
Context
Please provide any relevant information about your setup
Expected Behavior
Video's play as normal.
Current Behavior
Since this morning (Europe timezone), the Youtube plugin is unable to play any video's wth the error stating "Content not available on this app". Everything was working fine yesterday evening and into the night.
Disabling/enabling InputStream Adaptive for video playback makes no difference.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
Log
https://pastebin.com/4sn6gRgJ
EDIT
Fixed version:
Alpha release appears to have resolved the majority of the issues so far:
https://github.com/anxdpanic/plugin.video.youtube/releases/tag/7.x.x-dev
Not in Stable branch (yet), so leaving the issue open until pushed to Stable branch.
Potential (manual) Workaround(s):
@RNavega provided a fix that seems to work for now:
#442 (comment)
Specifically, the "payload" section seems to be the fix.
Another version of the fix to video_info.py which seems to be more reliable:
#442 (comment)
The text was updated successfully, but these errors were encountered: