2016-01-14, 04:48
(2016-01-13, 20:29)activoice Wrote: I'm currently on KODI 15, so I only updated the API keys in the youtube-for-kodi-15 section. And I can see in the login_client.py file that there is a section for Jarvis... I'm assuming that I can add the same API keys that I updated to the V16 section...
But since this plugin is no longer being developed what do we do for versions after that is it just a matter of adding a new section for version 17? or will the plugin be broken after that because it needs an update to more than just the login_client.py file?
+1-ish...
An excellent question, and a brick wall I seem to have run in to. I can confirm that "just" adding a new section for kodi 17 does not help - a very sad discovery.
My Intel NUC runs OpenELEC. Late in December I bumped the OS to a kodi 17/Krypton development build (courtesy of Milhouse), and immediately noticed the image rendering improvement (50-inch Samsung plasma). Woo-HOO !
At the time I was getting the common youtube problems, attributed them to the quota-exceeded condition, and pressed on with the flurry of Holiday activities.
Today I decided to follow the simple procedure for generating my own Keys & Secret (outlined above with great clarity... THANKS !!). Only when editing the "login_client.py" file did it occur that - since I'm on kodi 17 - the fix may not be so simple. I created a new section for "17/Krypton", dropped in the strings and logged in to youtube.
Despite doing the two-step authorizations... SUBSCRIPTIONS returns the dreaded "Exception in ContentProvider/Unknown kind" error, and both MY CHANNEL and PLAYLISTS error with "Access not configured. The API (YouTube Data API)...".
Can't seem to find any Jarvis builds compiled to OE... so it's either fallback to creaky old Isengard, or wait for the day when the miracle of renewed care-and-feeding of Bromix's masterpiece arrives.
HISTORY and WATCH LATER do not even appear as choices (despite checking them in configuration dialogue).
Oh Well... lots of other things to see.
