Reverification of consent screen in production environment for add-on (Google Workspace Marketplace)

[alekz]

Hello, we have an editor add-on for Google Sheets currently published in the Google Workspace Marketplace (production environment), it's working great and people are installing it (~250 installs so far). We have a new feature in development, which we want to launch very soon, and it requires asking for a new scope permission.

The problem is, to ask for a revision of that new permission, according to Google's requirements, we have to deploy it into a production environment so that we can show a Google rep how that new consent screen looks and how the add-on behaves accordingly. That puts us into an impossible situation with our current users, because if we do that, they will see a "Google hasn't verified this app" screen and may choose to uninstall the add-on or just stop using it.

The last time we asked for verification, the process took 10 days. It wasn't a problem then, because the add-on was unlisted and we had no users yet, but now we don't know what to do because it seems like this is an oversight in the reverification process. Why do we have to bother our current users as a side effect of this bureaucratic process?

Is there a way to ask for verification of our consent screen without alienating our current users with "unverified" consent screens and 100 user limits? We would like to do this in a development or pre-release environment, not in production. I seriously can't imagine this happening to add-ons with 10 million users.

Thanks in advance!

[mariusbc]

It would be great if this process used branches like Git, that way Google could go through the verification process without impacting users and products could grow safely and ask for the scopes required for new features. Everybody wins.

[dave77]

@alekzHave you asked Google if they will let you use a test deployment from within your Add-on to demonstrate the new behavior? Please let us know what they say, or why this isn't an option.

[jason_tech]

Their OAuth reverification process is weird. A more serious problem is when you have maxed out the 100 users for unverified authorizations, new users will see "Sign in with Google temporarily disabled for this app", which means the new features pushed are completely unusable. 

It's like a chicken and egg problem. Sent feedback to them but it does not seem to improve. 

[bgauthie]

Hi there,

We're facing a lot of time this issue. 

@alekz , if I'm correct, you can:

• submit your OAuth app to Google reverification (it won't affect your production OAuth app),
• wait for the verification,
• once it's verified, add the new scopes to your Google Workspace Marketplace app.