Our OAuth page has been verified but users still getting unverified messages

[pnovosel]

We've been having a hard time getting our integration with Gmail live and verified in our production environment. At first we had an extra scope in our submission, which we finally corrected. Now it's verified, but our Gmail integration OAuth consent screen is still indicating "unverified" (or some users are blocked).

Had anyone else experienced this? We have several other Google integrations that are working just fine, but this one (which sends email) is stuck. There isn't an option on the verification screen to say that there's a problem or report an error.

[Willbin]

Hello @pnovosel,

Welcome to Google Coud Community!

See Unverified app screen for this

---

Unverified app screen

The app or script might display an "unverified app" screen before it displays the consent screen. This is based on the specific scopes that your app includes in the request. This warning will display when:

• Your app uses sensitive or restricted scopes and you haven't configured them in your OAuth consent screen configuration page and requested verification.
• Your app uses sensitive or restricted scopes that you haven't selected on the OAuth consent screen configuration page.
• You selected sensitive or restricted scopes on the OAuth consent screen configuration page and requested verification, but the verification is not yet complete.

When the scopes requested in your app code differ from the scopes requested in your OAuth consent screen configuration page, your users see an "unverified app" screen. Make sure that scopes you request in your app are the same as what's in your OAuth consent screen.

---

[pnovosel]

The issue is that the scopes we're using and the ones listed in our OAuth consent screen match, but users are still getting the unverified screen.