• 1
  • 197
  • 198
  • 199(current)
  • 200
  • 201
  • 202
Release YouTube
I created the APIs but it still doesn't work. Is there anything else I can do ?
Reply
(2025-01-25, 19:15)otinley Wrote: ClaudeR,

Get a new API and register your device, it takes 5 minutes.
If you don't, YT will no longer work in Kodi.

I created the APIs but it still doesn't work. Is there anything else I can do?
Reply
Could you restore the arrangement of likes and replies in the video comment list view so that they are displayed directly behind the usernames? Alternatively, it would be desirable to create the option for customizable order.

Before | That is better
Image
Now | Not so good
Image
Reply
The Beta4 version worked great for me on my Windows desktop, laptop, Android box and Android tablet, but I have 3 ONN Google TV devices that I'm having trouble with. When I download the link, it doesn't appear in "install from zip file" like it does on the afore mentioned devices, even though I have "show hidden files" ticked. Is there a trick to this? If not, since the plugin is working so well, can it be pushed to the Kodi repo, or another repository, so we can install it on these devices?
Reply
@jim_p - what is your agenda here? Stop with the misinformation and off-topic posts. I have already asked you numerous times, and this will be my last time responding to you if you continue like this.
 
(2025-01-26, 07:28)jim_p Wrote: When you have a video playing with hardware decoding from the gpu, the cpu should be below 15% during the entire time the video plays.

This is completely arbitrary, and luckily you are not the arbiter of what is acceptable CPU usage. 

(2025-01-26, 07:28)jim_p Wrote: The kernel's scheduler makes it so that the cpu usage is not on one core all the time so as to not fry it

This doesn't make any sense. You are simply resorting to hyperbole with no basis in fact.
 
(2025-01-26, 07:28)jim_p Wrote: If the really high cpu usage, the high temperature it creates (you said you obsever a rise of 10oC in your low powered system) or the reduced battery life are not an issue for you, then I have no other way to convince you.

This is just pearl clutching complaining and hyperbole.

My device, with very good passive cooling rises from ~30 deg.C. to 40 deg.C. others have reported temperatures of 50-75 deg.C. with a rise from idle of ~5-10 deg.C. You don't need to convince me of anything, but you are welcome to check what the thermal limits are for any reasonably "modern" SoC, or even at what point they may start to throttle. Hint - it is closer to 100 deg.C. than 50 deg.C. and by modern I am including devices from the last 10-15 years.
 
(2025-01-26, 07:28)jim_p Wrote: neither mpv, which uses yt-dlp (and it also does a proxy as you say),

I did not say that. yt-dlp does not implement a proxy server.
 
(2025-01-26, 07:28)jim_p Wrote: youtube-viewr (which also uses the api tor scraping and mpv for playing)

It also uses yt-dlp.

You might want to have a look at https://github.com/yt-dlp/yt-dlp/issues/3766, specifically the "Intractable issues" part. Good luck implementing any of those workarounds if you get blocked again, when you can't even follow instructions to sign in. Your best bet at that point would be to try and get a new IP again, as I have advised you previously, even if you don't believe that the numerous times you have already been blocked are not related to your IP at all.

(2025-01-26, 07:28)jim_p Wrote: Everything works

Then just use whatever works for you. Why keep coming here to complain about things and making things up? Just move on with your life.

(2025-01-26, 07:28)jim_p Wrote: You definitely can, if you only care about searches and the like and not playback. Because the moment you will try to play something, it will play one or two videos, at most, and then you will get the "sign in to confirm you are not a bot" notification. Here, on the system that I have 7.2.0beta4, it plays exactly ZERO videos wiithout popping that notification. 

You are just making stuff up now. What you may be experiencing is not universal - not everyone is affected by the blocks.

However you definitely are. Despite that you refuse to follow the advice given to you, and instead continuously complain about the consequences of your own choices.

If you actually want to resolve your issue, rather than just making noise and complaining, simply stop posting and instead follow the instructions given to you a number of times already.


@kaminix - a user on GitHub has written up some updated instructions: https://github.com/anxdpanic/plugin.vide...2613975245, your issue appears to be with Step 9 as @mcarni noted.

(2025-01-26, 20:20)kaminix Wrote: when I go back to the youtube app to see the second device code it does not show it like it did for my first Android and there is no 'sign in' icon only a 'sign out' icon so the app doesn't work because it doesn't have the second device code entered. It thinks I am signed in but doesn't have the second code.

The two device code prompts are in the current beta version. The first one is not actually used for anything, but if you are only seeing one then that means you are still using v7.1.1.6


@Alyyy - no one can help when that is all the detail that you can be bothered to provide. Luckily you can help yourself by simply following the numerous instruction that have been posted in this thread.

 
(2025-01-26, 23:49)Sittich Wrote: Alternatively, it would be desirable to create the option for customizable order.

Won't be making it customisable, but I agree the old position is more useful.

 
(2025-01-27, 00:51)TopekaRoy Wrote: If not, since the plugin is working so well, can it be pushed to the Kodi repo, or another repository, so we can install it on these devices?

An official release will be made available when it is ready. In the meantime you can follow the instructions on the wiki to install the testing repository if you have problems installing from a zip file.
https://github.com/anxdpanic/plugin.vide...positories - see Option 2
https://github.com/anxdpanic/plugin.vide...t-versions - for the beta versions
Reply
@MoojMidge

Thanks for the quick reply. This is exactly what I was looking for. I'll give it a try.
Reply
I am unable to get past the error 'The OAuth Client was not found code 401' when I attempt to login.

This is regardless of whether I am using old or newly created api keys and the latest Beta 4 addon release.

None of the discussion seems to address this particular error.
Reply
Hi, sorry I could not find the answer in this long thread. I did follow the install steps, until I need to login twice. The Api part seams ok, I added a user account to the app to use it. The first time I click login I get a code, but as soon as I validate youtube access, I'm logged into this account without getting the second login code. Then I can see the trending video but if I try to play one it says: you need to login to prove you are not a bot. I tried to log out and in again, but it's still the same. How do I get the second request to login?
Reply
Hi, I do everything on this PC but we watch Kodi on an Android. Now that the Youtube app is signed in and working on the Android does the Google/Chrome app outside of Kodi on the Android need to remain signed in? I only use the Android for Kodi and normally never use it for Google or anything else other than during the Youtube sign in process. Thank you
Reply
Just spent the last hour renewing the API numbers etc. After signing in I am still getting the bot notification. Is there a time lag between satisfying Google and being able to access YT through Kodi?

If there is I will be patient, if not I will revert to accessing YT through the Windows app on my NUC box, because it works albeit with a miserable user interface.
Reply
There is nothing to wait for and there is no lag.

Retrace your steps:

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key
Still on your google developer console page, on the "Oauth consent page" tab,
 under "publishing status", below testing, click on Publish App.

Now you are done with the Google console page and you should have 3 fields.
Launch Kodi and add the 3 fields to the YouTube addon settings,
Still in Kodi, still in the YT addon , sign in:
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

Please check linked image. (download or open image for full size)
https://imgur.com/a/api-V9Op7GL
Reply
(2025-01-27, 14:22)otinley Wrote: There is nothing to wait for and there is no lag.

Retrace your steps:

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key
Still on your google developer console page, check that you you have on the left a "Oauth consent page" tab
there you have a "publishing status"

With those 3 fields go back to Kodi and add them to the YouTube addon settings,
Still in Kodi, still in the YT addon , sign in:
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

Please check linked image. (download or open image for full size)
https://imgur.com/a/api-V9Op7GL

Done all that but did not have to sign in twice, so I will reboot the box and sign in again. Thanks for your quick reply, I really do want to make this work. I will report back later.
Reply
(2025-01-27, 14:30)JNRW Wrote:
(2025-01-27, 14:22)otinley Wrote: There is nothing to wait for and there is no lag.

Retrace your steps:

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key
Still on your google developer console page, check that you you have on the left a "Oauth consent page" tab
there you have a "publishing status"

With those 3 fields go back to Kodi and add them to the YouTube addon settings,
Still in Kodi, still in the YT addon , sign in:
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

Please check linked image. (download or open image for full size)
https://imgur.com/a/api-V9Op7GL

Done all that but did not have to sign in twice, so I will reboot the box and sign in again. Thanks for your quick reply, I really do want to make this work. I will report back later.
You should not have to reboot. I did not even close Kodi.
Please check your Oauth consent page, does it look like mine?

https://imgur.com/a/f987TZb
Reply
Hi JNRW, I had what is probably the same problem you're having. First make sure you have at least the versions 7.2.0+beta 4 or 5 installed. If you aren't updated to this you won't be able to enter your device codes twice when signing in. I had to go back to my Api project and click on the Oath Consent Screen on left. Under Publishing Status change 'Testing' to 'In Production'. You may need to 'Publish App' to accomplish this but I can't quite remember. What I do know is you can't leave it reading 'testing' and as I said you want it to read 'In Production' then try to sign in twice again. On the second try you will see a different screen that has the word 'Advanced' on the bottom left, click this and it will show  the name of your project and you click on that name and proceed to allow it etc. It should show you 'success' again. Now try your youtube app and see if it is working for you. otinley and mcarni and moojmidge pointed me in the right direction for this. Hope it works.
Reply
(2025-01-27, 14:37)otinley Wrote:
(2025-01-27, 14:30)JNRW Wrote:
(2025-01-27, 14:22)otinley Wrote: There is nothing to wait for and there is no lag.

Retrace your steps:

First, create an API which will give you the 1st field needed,

Second,  create an OAuth 2.0 Client IDs which will give you two fields:
- Client ID.  You need to strip .apps.googleusercontent.com from the clientID if present.
- Secret key
Still on your google developer console page, check that you you have on the left a "Oauth consent page" tab
there you have a "publishing status"

With those 3 fields go back to Kodi and add them to the YouTube addon settings,
Still in Kodi, still in the YT addon , sign in:
You will have to sign in and register your device twice.
"The second time you Connect a device, you will be prompted with:
This app isn't verified This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
From there clicking Advanced and Go to <your project name> (unsafe) allows you to complete the process."

Please check linked image. (download or open image for full size)
https://imgur.com/a/api-V9Op7GL

Done all that but did not have to sign in twice, so I will reboot the box and sign in again. Thanks for your quick reply, I really do want to make this work. I will report back later.
You should not have to reboot. I did not even close Kodi.
Please check your Oauth consent page, does it look like mine?

https://imgur.com/a/f987TZb

At the risk of sounding thick, but it is more likely due to my old age, could you kindly tell me how to get to that page?
Reply
  • 1
  • 197
  • 198
  • 199(current)
  • 200
  • 201
  • 202

Logout Mark Read Team Forum Stats Members Help
YouTube0