Occured an Internal_Error When Requestemail from Googlesigninoptions Android

Occured an INTERNAL_ERROR when requestEmail from GoogleSignInOptions Android

If you get error code 8 (INTERNAL_ERROR), please double check your app registration in dev console. Note that every registered Android client is uniquely identified by the (package name, Android Signing Certificate SHA-1) pair. If you have multiple package names / signing certificate for your debug and production environments, make sure to register every pair of them. To verify:

1. Open the Credentials page and select your project
2. Make sure every pair has an Android typed OAuth 2.0 client IDs.
   To create a new OAuth 2.0 client ID for your Android client, select New Credentials->OAuth2 Client ID from the dropdown, select Android and input your Package name / Signing-certificate fingerprint there.

To get your signing key certificate SHA-1:

Standard Debug Key

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android


Other (Custom) Key

keytool -list -v -keystore $YOUR_KEYSTORE_LOCATION


Android Google Sign In fails with error code 8 (no message)

Check out the answer to this question: An INTERNAL_ERROR (8) occurred when requestEmail from GoogleSignInOptions on Android

If you get error code 8 (INTERNAL_ERROR), please double check your app registration in dev console. Note that every registered Android client is uniquely identified by the (package name, Android Signing Certificate SHA-1) pair. If you have multiple package names / signing certificate for your debug and production environments, make sure to register every pair of them. To verify:

1. Open the Credentials page and select your project
2. Make sure every pair has an Android typed OAuth 2.0 client IDs.
   To create a new OAuth 2.0 client ID for your Android client, select New Credentials->OAuth2 Client ID from the dropdown, select Android and input your Package name / Signing-certificate fingerprint there.

To get your signing key certificate SHA-1:

Standard Debug Key

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android


Other (Custom) Key

keytool -list -v -keystore $YOUR_KEYSTORE_LOCATION


Android Google Plus sign in issue. handleSignInResult returns False

Are you using Plus.API or Auth.GOOGLE_SIGN_IN_API? The latter is the latest revamped one. Check it out here:
https://developers.google.com/identity/sign-in/android/sign-in

---

If you are using Auth.GOOGLE_SIGN_IN_API:

In onActivityResult, use code similar to below and you can get a status code, which is defined by GoogleSignInStatusCodes: https://developers.google.com/android/reference/com/google/android/gms/auth/api/signin/GoogleSignInStatusCodes

@Override
public void onActivityResult(int requestCode, int resultCode, Intent data) {
    super.onActivityResult(requestCode, resultCode, data);

    // Result returned from launching the Intent from GoogleSignInApi.getSignInIntent(...);
    if (requestCode == RC_SIGN_IN) {
        GoogleSignInResult result = Auth.GoogleSignInApi.getSignInResultFromIntent(data);
        int statusCode = result.getStatus().getStatusCode();
    }
}

The most common issue is missing the right OAuth2 client registration. (Unfortunately, for now, the status code is INTERNAL_ERROR 8, which is not helpful. ) E.g. Take a look at this thread:
Occured an INTERNAL_ERROR when requestEmail from GoogleSignInOptions Android

Unable to overwrite files in Google Drive AppData folder INTERNAL_ERROR

According to this thread, if you get error code 8 (INTERNAL_ERROR), please double check your app registration in dev console. Note that every registered Android client is uniquely identified by the (package name, Android Signing Certificate SHA-1) pair. If you have multiple package names / signing certificate for your debug and production environments, make sure to register every pair of them.

To verify:

1. Open the Credentials page and select your project
2. Make sure every pair has an Android typed OAuth 2.0 client IDs.
   To create a new OAuth 2.0 client ID for your Android client, select New Credentials->OAuth2 Client ID from the dropdown, select Android and input your Package name / Signing-certificate fingerprint there.

To get your signing key certificate SHA-1:

Standard Debug Key

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

Other (Custom) Key

keytool -list -v -keystore $YOUR_KEYSTORE_LOCATION

Here's a reference which might also help:

• Error : ConnectionResult{statusCode=INTERNAL_ERROR, resolution=null}

If you are getting this bug even after 1) making sure that you have registered the package name with its corresponding certificate fingerprint, and 2) are (re)using an already existing project, then you should check that this project has an product name and an email address (double check that one specially) associated with it, both to be found in the "consent screen" section.

---

Related Topics