In-app Testing

Please reply to the email you received from the OAuth Verification team with details on how to log in to your application. We require sufficient access to continue testing the OAuth consent process and your application’s functionality. 

 

We recommend you perform the following for an efficient testing process.

1. In your email response to the OAuth verification team, be sure to include:
   • A login URL
   • Instructions on how to login and execute the OAuth consent workflow
2. If providing a test account, disable two-factor authentication for those credentials.

 

In addition, if your request falls under any of these scenarios, you should create a separate Cloud Console project to serve as a staging environment so that we can test your application’s usage of the requested scopes:

• Your application is live and you don’t want users to see the unverified app screen 
• Your application is already approved for sensitive/restricted scopes and you are requesting to add new sensitive/restricted scopes
• Your application has already exhausted the 100 new user quota limit and sign-in to the API integration is disabled

 

Creating a Test Project

Create a test project for verification by following these steps: 

1. Create a new Cloud project.
2. Configure the OAuth Consent screen and add the required scopes
3. Configure the Publishing Status to “In Production”
4. Configure a test deployment of your app to work with this test Cloud project
5. Provide all information necessary for our team to access the staging environment and use the app.

We require a username and password for an account that is registered with your application so we may test the OAuth consent screen and application functionality. There are two options for providing such an account.

Option 1: Allow-list the credentials you received via email

A reviewer email address should have been sent to you in the email you received from the verification team. Please authorize this email address to login into your application. Reply directly to the email you received with confirmation that the reviewer account has been allowlisted.

Option 2: Provide local test credentials

If you are unable to allowlist the provided account, you may provide us with an authorized username and password instead. Reply directly to the email you received from the OAuth Verification team with properly authorized credentials.

We were unable to test the OAuth consent workflow within your application. We require sufficient access to continue testing the OAuth consent screen and your application’s functionality.

Please reply to the email you received from the OAuth Verification team with the following.

1. Step-by-step navigational instructions for how to grant OAuth consent for the requested Google API scopes. Screenshots may also be provided to streamline the verification process.  
2. Any additional inputs our team will need to test how your application uses the requested Google API (e.g., phone numbers, file uploads, etc.). 

 

The following email serves as an example: