Oauth verification warnings

[Dan Briggs]

I recently received an email from YouTube about an oauth change. Here's the gist of the email:
1. As of July 19th 2019, a YouTube scope we are using ("../auth/youtube") is classified as sensitive.
2. That means we need to get our app verified.
3. If our app is not verified by August 18, 2019, it will be classified as unverified.

Fair enough.

However, when I go to verify our app, there are a few warning messages that concern me.

They are concerning because we are actively using this scope in production and rely on it. The warning messages make it sound like the scope will stop working and our app will become unverified as soon as we submit the verification form.

On the oauth consent screen, I've added the YouTube scope we need ("../auth/youtube"). Now I see three warning messages:
1. A message next to the new scope that says "Use of this API scope will be restricted until it is approved"
2. A message next to our domain that says "Use of this domain will be restricted until it is approved".
3. A generic warning that says "Because you've added a sensitive scope, your consent screen requires verification by Google before it's published".

Here's an image of these 3 warnings.

To me, this sounds like our app is going to break once we submit it for verification.

In the email from YouTube, they said the app won't become unverified until August 18, 2019. But these warnings make me think otherwise.

Is our app going to become unverified as soon as we submit it? If so, how do we avoid that?

Thanks in advance!

Dan

[Julie (cloud platform support)]

According to this document it is suggested to go through verification before you launch a user-facing app. If you have confirmed that you need to submit your application for verification and cannot skip the process, you can go through the process with these steps. If you do not submit in time your app will become unverified so if necessary I suggest completing the process sooner then later as it can take some time to be completed. 

The 3 warnings provided do not indicate that your app will become unverified if you submit for verification so if the email indicated a date on which the your app will become unverified then submitting it early is best practice for avoiding the app from becoming unverified. 

Please check out the FAQ for more information. 

I hope you have found this information helpful. 

[Dan Briggs]

Thanks Julie.

Yes, you're right that the warnings don't explicitly say it will become unverified if we submit it for verification. Good point. But it does say that the API scope will be restricted until verified.To me, that sounds like we won't be able to use the scope anymore once we submit it. We're actively using this scope in production so that would break our app.

I'm hoping these are just generic warning messages that are always shown when adding a sensitive scope and it's not taking into account the info that was in the YouTube email.

[Julie (cloud platform support)]

Looking at your screenshot the warning seems typical when unverified scopes are present however if the email does say that if the app is not verified by August 18, 2019, it will be classified as unverified then I suggest getting the submission done. 

From the 3 warnings, "Use of this API scope will be restricted until it is approved" "Use of this domain will be restricted until it is approved" and "Because you've added a sensitive scope, your consent screen requires verification by Google before it's published" I not found any evidence that by submitting the verification, that the scope would not be able to be used and the warning themselves do not seem to point to this. 

[Dan Briggs]

Got it, thanks for the quick response Julie. I just submitted it and can confirm that it did _not_ break :) Just wanted to be cautious. Thanks for your help.

[Julie (cloud platform support)]

You're welcome, glad to be of assistance :)