Unable to Sign In

[anxdpanic]

Signing in with Google is temporarily disabled for this app The use of Google Log-in has not yet been confirmed for this app

Using your own API keys should resolve this issue. For information on how to do this, see https://github.com/jdf76/plugin.video.youtube/wiki/Personal-API-Keys

[kaergel]

I can not confirm this workaround.

What I did: Create a API Key Configure API-Key in Kodi-Youtube-Addon Try SignIn

Result: 2nd Signin fails

[bennypowers]

I am unable to sign in. On the second device key (for Youtube Kodi Plugin #1) I see this error:

Sign in with Google temporarily disabled for this app

This app has not yet been verified by Google in order to use Google Sign in.

I followed the API Keys steps, however that does not work since the final step in that process is to sign in with two device keys, and the Youtube Kodi app is denied by Google.

[SilentR33p3r]

Same issue, brand new 4k Fire stick with fresh kodi install, after entering my API Keys when trying to sign in it fails on the second authorization.

[Subteblu]

Same problem here using Kodi 18.5 with Libreelec. Second code fail.

[anxdpanic]

I just tried three sign in attempts-both logins- and all of them succeeded.

The second activation prompts 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.

[tmedicci]

I just tried three sign in attempts-both logins- and all of them succeeded.

The second activation prompts 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.

I can confirm that it works only if you had set up the API method previously. Otherwise, no advanced option would be available (just the unverified message).

Using Kodi 18.4 on Raspbian.

[bennypowers]

The steps outlined in the forum needed to use the API keys are incorrect.

The forum advises to paste the API keys into settings.xml. doing so had no effect for me.

Instead, when I pasted the keys into api_keys.json, I was about to log in by clicking ADVANCED, and (unsafe)

[cg00001]

Signing in with Google is temporarily disabled for this app The use of Google Log-in has not yet been confirmed for this app

Using your own API keys should resolve this issue. For information on how to do this, see https://forum.kodi.tv/showthread.php?tid=348464&pid=2681560#pid2681560

This worked just like anxdpanic said for me just now. Furthermore, since you can't copy and paste text on linux versions of Kodi, simply pasting id, key, and secret to settings.xml worked fine for me. The recent quota exceeded issue dissappears if you use your own API.

Thanks anxdpanic. :)

[tmedicci]

The steps outlined in the forum needed to use the API keys are incorrect.

The forum advises to paste the API keys into settings.xml. doing so had no effect for me.

Instead, when I pasted the keys into api_keys.json, I was about to log in by clicking ADVANCED, and (unsafe)

HTTP server to paste API keys worked like a charm for me. I didn't need to edit any files directly.

[DaisyF8]

EDIT : extra info

I'm using my own API keys, but when activating (via "Advanced" and "Go to (unsafe)" ), the second auth keeps throwing this error :

Exception: Error reason: |accessNotConfigured| with message: |Access Not Configured. YouTube Data API has not been used in project xxxyourprojectnumberxxx before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=xxxyourprojectnumberxxx then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.|

Can anyone say how I can activate ?

I allready de-activated and re-activated. ---> Same message I generated new keys ---> Same message Warning triangle in front of my api-key (credentials page)because key is "unrestricted" so I restricted API to YouTube Data API v3 (this is probably wrong, I know, just trying) ---> Same message

Also : when I try to enable my own Api keys (and get the Error mentioned above), if I start the addon --> It will crash. I then need to go to settings and change these to use the predefined keys. This will work, and I CAN SIGN IN, but this will only work for a day or so... And then I get the error "Youtube:AccesNotConfigured".

My use case 99% of the time is I share a youtube video from my phone via Yatse to Kodi, the yatse resolver script works fine, hands it over to youtube, but then the addon borks out.

[Loganicx]

Might not be a fix for all, but if you have another install of Kodi as I have on another system. I just lifted these folders over to my new install:

\AppData\Roaming\Kodi\userdata
-script.module.youtube.dl -plugin.video.youtube

and

\AppData\Roaming\Kodi\addons -plugin.video.youtube -script.module.youtube.dl

[aliasmeum]

Have the same issue. New install off Libreelec 9.2.0 on Rasperry pi 4b 4Gb.

[anxdpanic]

This is going to take a larger set of changes to hopefully get resolved properly. Hope to be started into that by next week.

Apologies for any inconvenience and thanks for your patience.

[aliasmeum]

I just tried Loganicx fix, and this is working for me :) Thank you Loganicx!

Might not be a fix for all, but if you have another install of Kodi as I have on another system. I just lifted these folders over to my new install:

\AppData\Roaming\Kodi\userdata -script.module.youtube.dl -plugin.video.youtube

and

\AppData\Roaming\Kodi\addons -plugin.video.youtube -script.module.youtube.dl

[CoolRat]

Same goes for me. Loganicx fix did the trick. 1.000 Thanks for that one.

[cg00001]

I didn't use my API in youtube until now (only a long time ago when I created it), but since it saves time and prevents future issues I whitelisted the youtube addon, so it doesn't get deleted after reinstalling.

[Wribbe]

EDIT : extra info

I'm using my own API keys, but when activating (via "Advanced" and "Go to (unsafe)" ), the second auth keeps throwing this error :

Exception: Error reason: |accessNotConfigured| with message: |Access Not Configured. YouTube Data API has not been used in project xxxyourprojectnumberxxx before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=xxxyourprojectnumberxxx then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.|

Can anyone say how I can activate ?

I allready de-activated and re-activated. ---> Same message I generated new keys ---> Same message Warning triangle in front of my api-key (credentials page)because key is "unrestricted" so I restricted API to YouTube Data API v3 (this is probably wrong, I know, just trying) ---> Same message

Also : when I try to enable my own Api keys (and get the Error mentioned above), if I start the addon --> It will crash. I then need to go to settings and change these to use the predefined keys. This will work, and I CAN SIGN IN, but this will only work for a day or so... And then I get the error "Youtube:AccesNotConfigured".

My use case 99% of the time is I share a youtube video from my phone via Yatse to Kodi, the yatse resolver script works fine, hands it over to youtube, but then the addon borks out.

I had the same problem, tried to re-create the project which made it work, not optimal, but thought I migth add it to the discussion.

[cg00001]

Editing Settings.xml did the trick for me, but if you have issues with the addon, try the Defaults button in the API section of settings or go to /userdata/addon_data/ folder and delete plugin.video.youtube to reset the addon, then use your API credentials from Kodi / Youtube addon.

[DaisyF8]

@Wribbe

Atm I'm using the predefined sets of API-keys and it works and keeps working. My systems clock was set six months wrong (I feel great shame) and my ntp daemon was not working... I think that messed some stuff up.

[Numiah]

Still no dice for me. Creating API and editing settings didn't make any difference. Can't login the 2nd time. Bummer.

[W9JYD]

Edit ... never mind.

Got it to work.

But the new location for the keys is in api_keys.json instead of settings.xml. Threw me off a bit, but I got it!

Google was being a derp. I was using a different Google account and realized my mistake. API key made and logged in!

73, W9JYD

[Nastert]

Can you make instruction manual how to fix that problem or just update the YouTube app in Kodi repositority?

I have no plans how to fix it on my rasberry i am just a „user“

[MicaelJarniac]

I also had this issue and the suggested solution (creating and using my own API keys) did fix it for me. This is the first time I use YouTube on this two days old Kodi install (OSMC on Pi3), and it appears to be all working.

[Nastert]

Can you tell me how to create and use my own api keys?

Von meinem iPhone gesendet

Am 26.12.2019 um 03:16 schrieb Micael Jarniac [email protected]:

 I also had this issue and the suggested solution (creating and using my own API keys) did fix it for me. This is the first time I use YouTube on this two days old Kodi install (OSMC on Pi3), and it appears to be all working.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[M-Reimer]

I can confirm that login with own API key still works well. But it was pretty fiddly. An updated tutorial on how to do it may be a good idea. I needed about two hours to finally get connected with my own API key.

[W9JYD]

Yeah, @M-Reimer, the tutorial on Kodi.TV forum is kinda outdated because Google changed up the UI a bit... but I could whip up one if time allows. My job makes me work weird hours so I can't guarantee anything, but the tutorial that is posted there is still relevant, but some of the steps are a bit different, but not by much.

73, Kevin Havens W9JYD Muncie, Indiana EN70he Ham on JY Doll TPE... The best combo on Earth.

On Fri, Dec 27, 2019, 07:06 Manuel Reimer [email protected] wrote:

I can confirm that login with own API key still works well. But it was pretty fiddly. An updated tutorial on how to do it may be a good idea. I needed about two hours to finally get connected with my own API key.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jdf76/plugin.video.youtube/issues/700?email_source=notifications&email_token=AOBEAZOVRU4YGDWWG5CQ47TQ2XVTLA5CNFSM4JWZOYYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHXCUHQ#issuecomment-569256478, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOBEAZME3FWTIJ2XL37HHUTQ2XVTLANCNFSM4JWZOYYA .

[miguelisidoro]

Is creating our own API Key the only solution? Is the developer team going to solve this issue to avoid this solution?

I am a tech guy but would prefer to use the normal activation method using the google.com/device page.

[anxdpanic]

Currently it is the only solution, also you still use the google.com/device to activate with your own keys.

The plan is to definitely try to resolve the issue, but this issue will require a lot to resolve properly. So it will be some time before there is a proper fix. 👎 :(

[kenwneill]

API keys guide worked for me. Do I now need to disable auto-updates for the plug ins?

[anxdpanic]

@kenwneill You don't need to disable auto update