Re: [crx] OAuth Verification Requirement for Chrome Extension CWS Review ; Parallel Process Timeline?

[Jay Elsheikh]

I had a few extensions that use south . I always requested verification on gcloud either before in parallel. If this the first submission it's normally will take some time 

On Mon, 27 Apr 2026, 08:43 ta hid, <amota...@gmail.com> wrote:

Hi, 

I'm submitting a Chrome extension to the Chrome Web Store that uses a sensitive Google Drive scope, which requires OAuth verification in Google Cloud Console (application type is Chrome extension and in testing mode ).

I just submitted my extension ( used this extension ID to create the Chrome extension application in the Google Cloud Console), and it is currently pending review in the CWS. I have a few clarifying questions:

1. Does OAuth verification need to be completed before CWS approval? Or can these two review processes run in parallel? I'm asking because the official docs state that "you must have a registered item in the Chrome Web Store Developer Dashboard" to submit for OAuth verification — my item is registered (and pending review), but not yet published.
2. Will CWS reviewers encounter the "unverified app" warning when testing my extension's Google Sign-In flow during their review? If so, does that impact their decision to approve or reject?
3. If I start OAuth verification now (while CWS review is still pending), will that affect the CWS review timeline in any way, or are they completely isolated processes?

I want to make sure I'm following the optimal order to avoid delays. Any guidance on the expected timeline for either process would be helpful as well.

Thanks

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/f93e2fa2-f51c-413d-bf34-57fdc7937023n%40chromium.org.