There is a very annoying Google error you might run into while working with Google Sheets. It usually shows up when you are trying to authorize an app or a script through Google App script. The error says “Sign in with Google temporarily disabled. The app has not been verified yet by Google in order to use Google sign in”.
Don’t worry, we’ve seen this issue before and we also know this issue is not an isolated case. There are tons of threads on Google support forums that refer to this issue. In this post, we’re going to suggest some solutions. But before we do that, let’s try to understand what might be causing the “sign in Google temporarily disabled” issue.
What’s causing the Google sign in issue for apps & scripts
First let’s understand what is causing the issue.
A security update by Google is the main reason behind this issue. Google has provided instructions for developers on how they can update their apps and scripts to the new security requirements.
This means that if you are getting this error, then the app developers haven’t updated the app. All you need to do is reach out to them and ask them to update the app. It also depends a lot on who created the app & script and who is trying to access it. The chart below will help you understand the unverified auth flow which causes the error to pop up.
Fix for “Sign in with Google temporarily disabled”
Solution 1: Turn on Google Apps Script API
This is a simple one. First make sure to check the Google Apps Script settings.
Turn on the “Google Apps Script API” setting and see if it helps resolve the issue.
Solution 2: Check OAuth consent screen
There is a dedicated section on Unverified Apps on the Google Cloud Support. It talks about unverified apps and what to do about them and that is the best place to start.
An unverified app is an app or Apps Script that requests a sensitive or restricted OAuth scope, but hasn’t gone through the Google verification process. Users of unverified apps or your test builds might get warnings based on the OAuth scopes you’re using. This is to protect users and their data from deceptive apps.
If your app uses sensitive information you will need to first configure them in your OAuth consent screen. Go to Google Cloud Platform Console (APIs & Services > Credentials > OAuth consent screen)
In case you try to select “Internal” as the user type you will probably get this error. This happens because you’re not a G Suite user, you can only make your app available to external (general audience) users.
Therefore we suggest you select “External” mode. In this mode, your app is available to any user with a Google Account. External apps that request sensitive or restricted user data must first be verified by Google
This means that Google is not encouraging apps & scripts that capture sensitive information to be run through Gmail accounts. Hence we recommend that you either get a G suite account or get your app go through the verification process.
Solution 3: Get your app verified
To get the app verified follow the process on the on verification of for apps.
- Update the OAuth consent screen details in the Google Cloud Platform Console APIs & Services Credentials
- Verify your website ownership through Search Console by using an account that is a Project Owner or a Project Editor on your OAuth project.
- To start the verification process, submit a verification request by clicking on Submit or Save on the GCP Console OAuth consent screen.
When to go through verifications for apps
Think about why and why you need to go through verification. Remember you only need to go through the verification process before you launch a user-facing app.
This means you do not need to go through verification if your app is in development or internal. If your app is experimental or a test build, you don’t need to go through verification unless you decide to launch it to the public. Also if your app is an internal web app for users in the same G Suite domain then no verification is needed either.