Hello Google Developer Community,
I am currently experiencing a persistent issue with the OAuth app verification process for my website, and I am hoping to get some guidance from developers who may have encountered something similar. The core problem is that my OAuth application has remained in the verification process for an unusually long period despite my understanding that all of Google’s published requirements have been satisfied. The website integrates with Google Sign-In so users can authenticate using their Google accounts, and before submitting the application for verification I carefully completed the OAuth consent screen, configured the authorised redirect URIs, added the required application information, verified my domain, and ensured that the privacy policy and terms of service pages were publicly accessible. However, the verification status has not changed, and I have not received any specific feedback identifying missing requirements or issues that need to be corrected.
To make sure the application complied with the verification guidelines, I thoroughly reviewed every configuration in the Google Cloud project before submission. The branding information matches the website, the application logo and support email are correctly configured, and the authorised domains correspond to the verified domain used by the application. I also ensured that the requested OAuth scopes are limited to only those required for the application’s functionality and removed every unnecessary scope before submitting for review. From a technical perspective, the OAuth authentication flow functions correctly in testing mode, and users added as test accounts can complete the sign-in process without any authentication errors. The only obstacle is that the application cannot be made available to all users because the verification process remains pending.
I have also reviewed the demonstration material that was submitted with the verification request. The demonstration video clearly shows the login flow, explains why each requested scope is needed, and demonstrates how user information is handled within the website. The privacy policy explains how account information is collected, stored, and processed, and all required links are accessible without authentication. Since the application is functioning correctly and the supporting documentation appears complete, I am struggling to understand whether there is a technical issue with the submission itself or whether there is something in the OAuth configuration that is preventing the review from progressing. Unfortunately, because no detailed feedback has been provided, it is difficult to determine which part of the submission should be investigated further.
Another aspect that makes this issue particularly difficult is that I have avoided making configuration changes after submitting the verification request because I do not know whether modifying the OAuth consent screen or authorised redirect URIs could restart the review process or introduce additional delays. At the same time, I am unsure whether leaving the configuration unchanged is the correct approach if there is an unnoticed issue preventing approval. The application continues to operate correctly for test users, which suggests that the OAuth implementation itself is functioning properly, but the lack of progress in verification leaves me uncertain whether the problem is related to the application’s configuration, the submitted documentation, or another requirement that I may have overlooked.
From the development side, I have verified that the OAuth redirect URIs exactly match those configured in the Google Cloud Console, HTTPS is enforced across the website, and all authentication requests complete successfully when using approved test accounts. Token exchange, refresh token handling, and callback processing all function as expected during testing, and no OAuth-related errors appear in the application logs. Because the authentication flow itself is stable, the issue seems isolated specifically to the verification process rather than to the technical implementation of OAuth within the website. This makes the problem difficult to troubleshoot because there are no runtime errors or diagnostic messages indicating what might be delaying the review.
I would greatly appreciate guidance from the Google Developer community regarding the best way to diagnose and resolve this verification issue. Specifically, I would like to understand whether there are common reasons why an OAuth application can remain in the verification process despite appearing to meet all published requirements, whether there are configuration details that developers frequently overlook, and whether there are recommended methods to confirm that the submitted verification materials satisfy Google’s review expectations. Any advice on identifying potential submission issues, avoiding unnecessary delays, or determining when it is appropriate to update an application that is already under review would be extremely valuable. My goal is simply to complete the OAuth app verification successfully so that all users can authenticate with their Google accounts without the application remaining restricted to testing mode. Sorry for long post!