Kodi Community Forum
YouTube Plug-in Thread - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27)
+---- Forum: Video Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=154)
+---- Thread: YouTube Plug-in Thread (/showthread.php?tid=353278)



RE: YouTube Plug-in Thread - amrothery - 2020-03-02

Like so many other people recently, my YouTube plugin broke the other day.

I set up a new API key yesterday, and today set up a brand new Kodi installation with YT as the only plugin. Still isn't working, still getting the error message when I enter the code at google.com/devices.

Using LibreELEC 9.2.0 on a Pi 3.

http://ix.io/2d9e


RE: YouTube Plug-in Thread - Roby77 - 2020-03-02

Kodi 19 on libreelec 9.80 and custom api

6.6 works great

6.6.1 YouTube give error

6.7 alpha 2 works greats


RE: YouTube Plug-in Thread - xalaros10 - 2020-03-02

@anxdpanic... MPEG-DASH tab on "Video quality" what we choose (I have 4K TV) ?


RE: YouTube Plug-in Thread - terrancej30144 - 2020-03-02

(2020-03-02, 04:32)Sea Monkey Wrote: Hi,

I am currently using Kodi on FireTv and my YouTube addon was worknig with out any issues until I reinstalled Kodi. I see all these personal API key generation process - I am not sure how to implement on Firetv Kodi combination. Any help would be much appreciated. Thanks


To those seeing 'OAuth client deleted' who have already set up a developer key,

Generate a new OAuth Client ID and put it in Kodi along with your new 'secret' then CLOSE AND RESTART KODI.  If you still have problems, go to the settings for your API key, regenerate key, input that, and CLOSE AND RESTART KODI.

Simply regenerating all three values might work for you, but my first inclination due to the error message was to generate a new Client ID, and thus a new 'secret' as well, altogether.



RE: YouTube Plug-in Thread - bob_the_one - 2020-03-03

Hi like expected, today I got this E-Mail:

Dear YouTube API Developer,

We are currently conducting a mandatory compliance review of your YouTube Data API Project. The review is to assess your compliance to our YouTube API Services Developer Policies (link) and to learn about how our service is being used.
At your convenience in the next seven (7) business days, please complete and submit the following information :

1. A fully functional demo account, including a username and password with which we may access your API Client. The demo account you provide will be used only for compliance inspection and the credentials will not be shared.
2. A fully completed YouTube API Audit Form
3. Screenshots of how your API Client and its users access and use the YouTube API Services
4. Documents relating to your implementation, access and use of YouTube API Services
 
For reference, your project number is ************ 
Please ensure that all required supporting materials are submitted and sufficient, and all questions are answered thoroughly. If this is not the correct or preferred API contact email, or if you would like us to cc any other contacts on future emails, please let us know. 
 
Thanks,
YouTube API Services team


I don't want to answer google/youtube. What will happen? They close my api access?


RE: YouTube Plug-in Thread - Anonnymouse - 2020-03-03

(2020-02-29, 20:37)anxdpanic Wrote: @Anonnymouse
I might be able to figure out the issue with a complete debug log (wiki) showing the Yatse playback attempt.

Hi,

Thanks, here it is: https://paste.kodi.tv/unuwicozis.kodi .

The stream ID is ckYN_TwbGiQ .


RE: YouTube Plug-in Thread - the_other_guy - 2020-03-03

(2020-03-03, 00:06)bob_the_one Wrote: Hi like expected, today I got this E-Mail:

Dear YouTube API Developer,

We are currently conducting a mandatory compliance review of your YouTube Data API Project. The review is to assess your compliance to our YouTube API Services Developer Policies (link) and to learn about how our service is being used.
At your convenience in the next seven (7) business days, please complete and submit the following information :

1. A fully functional demo account, including a username and password with which we may access your API Client. The demo account you provide will be used only for compliance inspection and the credentials will not be shared.
2. A fully completed YouTube API Audit Form
3. Screenshots of how your API Client and its users access and use the YouTube API Services
4. Documents relating to your implementation, access and use of YouTube API Services
 
For reference, your project number is ************ 
Please ensure that all required supporting materials are submitted and sufficient, and all questions are answered thoroughly. If this is not the correct or preferred API contact email, or if you would like us to cc any other contacts on future emails, please let us know. 
 
Thanks,
YouTube API Services team


I don't want to answer google/youtube. What will happen? They close my api access?

would just explain that needed it to use this addon


RE: YouTube Plug-in Thread - rexdel33 - 2020-03-03

I have a question regarding the play trailer context menu and trailer play feature in the info screen included with most movie/tv addons.
after doing the personal api for YOU TUBE the addon is working again no problem except that now the context and info menu no longer play the trailer for the tv show or movie.
always found that feature handy with an unknown TV/MOVIE...am i missing a step somwhere?

any help much appreciated


RE: YouTube Plug-in Thread - TheMeddlingMonk - 2020-03-04

I, too, have had problems getting the add-on to work recently. I set up an API key as required, but after signing in again the app reports an error. The KODI log is here:

https://paste.osmc.tv/mideqiqacu

Any suggestions would be much appreciated.


RE: YouTube Plug-in Thread - anxdpanic - 2020-03-05

@xalaros10 Choose what works best for you.

@bob_the_one Not sure, probably disable those keys or nothing. You could delete the keys/project and create a new project and keys if necessary.

@Anonnymouse, @TheMeddlingMonk Please try beta1, see below.

@rexdel33 Please try beta1, see below. If that doesn't resolve the issue, please provide a complete debug log (wiki) reproducing the issue.


I've updated post #2 and the repositories with beta1
Code:
~beta1
[add] send PlaybackInit, PlaybackStarted, PlaybackStopped notifications containing video id, channel id, and the status of the playing video
[fix] search sometimes returning blank
[fixup] fix uri2addon playback route, no longer requires api
[rem] remove provided api keys
[lang] pl_pl strings |contrib: drrak|
[lang] de_de strings |contrib: tweimer|
...


RE: YouTube Plug-in Thread - TheMeddlingMonk - 2020-03-05

(2020-03-05, 00:10)anxdpanic Wrote: @TheMeddlingMonk Please try beta1, see below.

I've updated post #2 and the repositories with beta1
 
Thankyou, this has resolved the problem!


RE: YouTube Plug-in Thread - hoopsdavis - 2020-03-05

The process Listed here:  https://github.com/jdf76/plugin.video.youtube/wiki/Personal-API-Keys helped get my YouTube trailers working again on 5 devices in my home.

After creating and having your API Key, ID and Secret created I'd recommend using Method 2 to configure your Kodi YouTube App.


Feel free to respond if there's any confusion during the process.


RE: YouTube Plug-in Thread - truog91 - 2020-03-05

this addon still work with kodi 18.5, i installed today but it seem not working.


RE: YouTube Plug-in Thread - bluebug - 2020-03-05

hi how safe is it putting on your  crudentials on google cloud for this to work thanks


RE: YouTube Plug-in Thread - anxdpanic - 2020-03-05

@truog91
The add-on requires your own api keys now.
First I'd install the latest beta version found through post #2
Second follow https://github.com/jdf76/plugin.video.youtube/wiki/Personal-API-Keys

@bluebug
I and others have been using personal keys for years, should be relatively safe. Also with your own keys your anonymized api usage statistics goes to your project and google. Using the old add-on keys it went to the add-ons project and google.