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?