Sign in with Google temporarily disabled for this app

[johnnypea]

Anyone experiencing this issue when trying to initialise the Google calendar? Is there some problem with the app @insanum ? Thanks.

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

[insanum]

Yes, I got a notification from Google about this a couple days ago. I submitted the gcalcli API scope usage for verification by Google. The form said it could take a couple weeks.

If you know someone who works for Google... ask them to help expedite/guide this along. :-)

[jester02k]

Hello I'm getting this error too after a reinstall of my system can someone explain whats going on is it my system or google's. I have never had a problem with Gcalcli an miss it.

[zripka]

Same here, I'm trying to install it for the first time and I'm getting the same message.

[rpietro]

same here

[MarSoft]

If you created client id and client secret from dev account associated to your google account then on "App not verified" screen you can bypass it by clicking "Additional" and then "Go to (project name) page".

[rpietro]

@MarSoft I don't get that option on Chromium or Firefox.

[eethann]

Can users create their own app as a work-around?

[eethann]

Confirming that using the --client-id and --client-secret arguments to authenticate works. This article is a bit outdated but is the general idea: create an OAuth web login app in the Google developer console, then enable the calendar API for it. Works!

This is probably the best approach, actually, if you are concerned about security (making sure you're not granting a 3rd party app access to your cal).

[maphew]

the process at https://github.com/insanum/gcalcli#login-information is more up to date than the blog post link on eethan's comment. There is still a "This app isn't verified" warning screen, but expand [Advanced] link at bottom and then use [Go to gcalcli (unsafe)] link under that.

[anthrolisp]

I'm also getting the following error:

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

I'm unable to get the --client-id and --client-secret arguments to work, and the "[Advanced] link at the bottom is not visible for me.

Any ideas? Many thanks in advance!

[maphew]

I tried to setup another computer. Google isn't showing the [Advanced] and [Go to gcalcli (unsafe)] links anymore for me either.

[aristosv]

Are there any workarounds to make this work?

[awkwardengineer]

any update on when Google might approve? I'm still hitting the same "Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In."

[jester02k]

I have been waiting for over a month is this going to be fixed or what or has it been abandoned? Any info would be appreciated.
UPDATE
I finally got this to work using this post #497 (comment) The google page has changed so I had to do some poking around but not too difficult to get going. Also you can not use Firefox either Chrome or Chromium just keep authorizing and it will produce the code needed for the app.

[jcrowgey]

So far, it seems like google hasn't invalidated any existing oauth tokens, so I've still been able to use gcalcli as normal. I did move my token out of the way and try to go through the sign in process using firefox. I also didn't see the "Advanced" option that some users reported. It would be nice to get to the bottom of that: exactly who sees "Advanced" and why.

EDIT: I suppose the reason why is that I just used the secret and id provided in gcalcli rather than making a new id and secret in the google dev console. @aristov @maphew: have you tried setting up your own client id and secret in the google dev page?

[aristosv]

Yes. Once you set up a new id and secret, then the Advanced option appears and you can create the 2 authentication files.

[ripperle]

@aristosv Today I tried to install gcalcli and had the same problem. How do you set up a new ID and secret?

[pjotrp]

The following worked for me: login to your google account and enable Google Calendar API with OAuth 2.0 Client IDs . Copy the client ID credentials. Next remove any old settings

  rm ~/.gcalc*

Next login with credentials

 ~/.local/bin/gcalcli --xxxx.apps.googleusercontent.com --client-secret=XXXX calw

Now, critically, you get a login in the browser which says the app is temporarily disabled. Click on the 'Advanced' link (which only shows up when you use credentials) and go to gcalcli and allow all. It will end with 'The authentication flow has completed.'. This should show your calendar, now you can run without credentials

  ~/.local/bin/gcalcli calw

[sadid]

I can confirm that @pjotrp solution worked.

[slosar]

Sorry for being a noob, but how do I " enable Google Calendar API with OAuth 2.0 Client IDs "? I've been looking around my google settings and google calendar settings and can't find this option.

[abers]

Same issue as with @slosar, absolutely no idea how to securely setup OAuth 2.0 Client IDs. When trying I'm stuck at stage where forced to setup a OAuth consent screen but unable to restrict it to Internal only. Any step-by-step instructions available? The ones on the github linked by @maphew don't explain how to deal with - "To create an OAuth client ID, you must first set a product name on the consent screen."

Edit:

1. Go to OAuth consent screen from sidebar
2. Create as External user type
3. On next screen give it a name and hit save
4. Go to Credentials from sidebar
5. Click Create Credentials from top, then OAuth Client ID in the dropdown
6. Choose Other, enter any name you want, and hit create
7. You now have your client ID and secret
8. In your terminal run "gcalcli --client-id "djfldsjl" --client-secret "djfaksdf" agenda
9. It'll open login screen in browser, login, when get error page click advanced, select gcalcli and allow all.

[jester02k]

This has worked for me but make sure you are using Chrome or Chromium not Firefox. That is where I see the other button (I can't remember it's name) and it steps through allowing it at the end you get a security code. But I can say that I have to run this every once and a while to reauthorize gcalcli it just fails.

[pjotrp]

I use firefox only. It worked as described.

[tuckerconnelly]

There's a button on this page that automates a lot of the process for getting the client id + secret, just need to click it: https://developers.google.com/calendar/quickstart/go

Also not sure if this matters, but @pjotrp it looks like your comment above is missing client-id=, should be:

 ~/.local/bin/gcalcli --client-id=xxxx.apps.googleusercontent.com --client-secret=XXXX calw

[Hitkul]

Just tried the method suggested by @pjotrp (created client-id by @tuckerconnelly suggestion) but I did not see any 'Advanced' link. Tested with both Brave and Chrome browser. Any idea what can I try next?

[squiter]

Just like @Hitkul I followed the instructions and can't see the 'Advanced' link in Chrome neither Firefox :(

[jcrowgey]

I'm guessing that the folks this isn't working for haven't set up their developer console.

[dannyshaw]

the configuration parameters are --client_id and --client_secret (note then underscores).

and NOT --client-id and --client-secret as incorrectly specified in the docs and all the examples above.

It must have changed at some point.

[Hitkul]

@dannyshaw It worked. Thank you

[squiter]

and NOT --client-id and --client-secret as incorrectly specified in the docs and all the examples above.

This did the trick, thanks

[desgua]

Thank you so much abers this step by step was what I needed :-)

[tobiasrenkin]

Here is a simple way to do it: go to https://developers.google.com/calendar/quickstart/python. Click on "Enable Google Calendar API". Get id and secret to use in gcalcli.

[aristosv]

Would this help?

https://github.com/aristosv/google_auth/blob/master/README.md

and then you can run

gcalcli --client_id=clientid_here --client_secret=clientsecret_here agenda

[ak202]

first time trying gcalcli, and I got the "temporarily disabled" notice without any "advanced" options. I did @aristosv suggestion and then the advanced button showed up, and I was then able to authenticate.

[sunnyguan]

If you have the fancy new dropdown box, I tried using TV and it was able to work as well. The name of the TV client did not matter.

[bwagner]

Behind a proxy here. Environment Variables http_proxy and https_proxy configured. Running
python -m pip install --upgrade pip
works (to demonstrate proxy settings are picked up by python).
Trying
gcalcli --client-id=xxx.apps.googleusercontent.com --client-secret=yyy calw
with and without (--noauth_local_webserver), I get to authenticate, but in the shell I get this error:

  File "c:\users\czxbwg\appdata\local\programs\python\python38\lib\site-packages\httplib2\socks.py", line 465, in __negotiatehttp
    raise HTTPError((statuscode, statusline[2]))
httplib2.socks.HTTPError: (407, b'Proxy Authentication Required')

This is:
gcalcli v4.3.0
on
MINGW64_NT-10.0-17763 C42L37WS1065 3.0.7-338.x86_64 2019-11-21 23:07 UTC x86_64 Msys
on
Microsoft Windows 10 Enterprise
Version 1809 (OS Build 17763. 1397)

[xdhmoore]

Still getting this screen on 2020-10-9. I was able to set up the clientid/secret successfully in Google Cloud's console as described. But it would be nice if it just worked. Since this issue has been open so long though, maybe at this point all the setup stuff should be added to the README. I have a passing familiarity with Google Cloud's console, but for people that don't, it may be prohibitively confusing.

[xdhmoore]

aaaaand, the process is already mostly on the README, here for anyone else trying to figure this out. When Google denies access click the Advanced option, as others have mentioned.

[KevinBuchs]

Still happening today. There is no advanced option

[aristosv]

Yesterday I did this for a client and it worked just fine. There was an "Advanced" button.

https://github.com/aristosv/google_auth/blob/master/README.md

[mglantz]

Confirming that using the --client-id and --client-secret arguments to authenticate works. This article is a bit outdated but is the general idea: create an OAuth web login app in the Google developer console, then enable the calendar API for it. Works!

This is probably the best approach, actually, if you are concerned about security (making sure you're not granting a 3rd party app access to your cal).

Confirming that this is still the case as of this writing.
Create Google Calendar API access, add oauth2 application, and then define arguments:

gcalcli --client-id the-id-you-created --client-secret the-secret-created

[dbarnett]

Seems like this won't be an issue anymore (as long as you're supplying your own --client-id and not using the old built-in one), but please reach out with a fresh issue if anyone's still seeing problems.