Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Oauth API - App Verification process

Hello everyone, 

I'm writing to you because I'm a bit confused about the application verification process to use the Google OAuth API.

Context: I made an application for one of my clients, who wants its users to be able to create an account and log in via Google authentication.

So I created an account on google cloud console, added the application and used the authentication service in test mode. 

I just deployed the application on a production environment, so I wanted to do the same for the OAuth API. 

But I realize that the verification process can take up to 8 weeks...

My question is: is there a way to reduce this time? My client's application is an MVP, it won't have hundreds of users (but I can't stay in test mode). 

In the emails I received from Google, it states:

"Dear Developer,
Thanks for submitting a verification request.
If your app doesn't need to display an icon, you can skip the verification process and no action is required. If you do skip the verification process, the existing functions of your app won't change, as long as the scopes used by your project don't change."

From what I understand, if I remove the app's logo on the authentication page (I think that's what the term "icon" in the text above refers to?) I can just skip the verification process? 

It seems a bit strange to me to skip a whole verification process just by not displaying a logo? On the other hand, I would be fine with that! 

Could someone please enlighten me? 

Thanks in advance,

1 2 1,103
2 REPLIES 2

If you have already added an icon to your consent screen, you would have to go into verification. As of this date, the existing feature request to change this behavior does not yet have an ETA. You cannot remove the icon unfortunately.

Otherwise, if you have not yet added an icon, you can still use your application. The application would be unverified and a few restrictions would apply in this scenario. Depending on the OAuth scopes your application is requesting from users, the verification time can range from 3-5 days (sensitive scopes) to several weeks (restricted scopes).

Hi there, we're also interested in building a Gmail integration which requires restricted scopes, but we're confused about the correct sequence of steps.

Do we start by building the integration locally, creating a demo video for verification, and submitting it? Then Google would let us know our application tier (2/3) and whether we require a third-party verification service?

Thank you for the clarification