Google SignIn API Exception 10

Question

Approaching to the final stage of the authentification, but something is going wrong in handleSignInResult method. It returns Exception code 10 (Developer error) in logs. Google provides comprehensive description:

The application is misconfigured. This error is not recoverable and will be treated as fatal. The developer is an idiot...

What should I do to handle this (get an account) and finally retrive values from account?
Thank you in advance for your help!!!

MainActivity:

package ru.podgorny.carcall;

import ...

public class MainActivity extends AppCompatActivity {

        SignInButton signInButton;
        public static final int RC_SIGN_IN = 07;
        public static final String TAG = "MainActivity";
        TextView tw1;
        TextView tw2;


        GoogleSignInOptions gso;
        GoogleSignInClient mGSC;


        @Override
        protected void onCreate (Bundle savedInstanceState){
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
        Log.d(TAG, "Activity Works");
        findViews();

            gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
                    .requestEmail()
                    //.requestProfile()
                    .build();

            mGSC = GoogleSignIn.getClient(this, gso); //smth with mGSC variable....

             View.OnClickListener onClickListener = new View.OnClickListener() {
                @Override
                public void onClick(View v) {
                    onClick2(v);
                }
            };
             signInButton.setOnClickListener(onClickListener);




    }

    private void findViews() {
            Log.d (TAG, "findViews started");
        signInButton = findViewById(R.id.idButtonGoogle);

        tw1 = findViewById(R.id.textView1);
        tw1 = findViewById(R.id.textView2);

        Log.d(TAG, "Views finded");


    }

    public void onClick2(View view) {
            Log.d(TAG, "onClick started");
        switch (view.getId()) {
            case R.id.idButtonGoogle:
                signIn();
                break;
        }
        Log.d(TAG, "OnClick Started");
    }

    public void signIn() {

        Intent signInIntent = mGSC.getSignInIntent();
        startActivityForResult(signInIntent, RC_SIGN_IN);
        Log.d(TAG, "startActivityForResult works");

    }

    @Override
    public void onActivityResult(int requestCode, int resultCode, Intent data) {
        super.onActivityResult(requestCode, resultCode, data);
        Log.d(TAG, "OnActivityResult started");
        // Result returned from launching the Intent from GoogleSignInClient.getSignInIntent(...);
        if (requestCode == RC_SIGN_IN) {
            // The Task returned from this call is always completed, no need to attach
            // a listener.
            Log.d(TAG, "TASK started");
            Task<GoogleSignInAccount> task = GoogleSignIn.getSignedInAccountFromIntent(data);
            handleSignInResult(task);
            Log.d(TAG, "OnActivityResult returned");
        }
    }

    private void handleSignInResult(Task<GoogleSignInAccount> completedTask) {
        try {
            GoogleSignInAccount account = completedTask.getResult(ApiException.class);//ERROR -- Code 10
            Log.d(TAG, "Account received");


            updateUI(account);
            Log.d(TAG, "updateUI Launched");
        } catch (ApiException e) {

            Log.w(TAG, "signInResult:failed code=" + e.getStatusCode());
            updateUI(null);
        }
    }

    private void updateUI(GoogleSignInAccount account) {
            if (account!=null) {
                tw1.setText("OK");
                tw2.setText("Name: " + account.getGivenName() + ", Family name: " + account.getFamilyName() + ", Email: " + account.getEmail() /*+ " image: " +
                        account.getPhotoUrl()*/);
            }else {
                tw1.setText("SMTH wrong");
            }

        }

}

score 48 · Accepted Answer · answered Mar 23 '18 at 13:33

48

This error might happen if you are not using same project at console.developers.google and console.firebase.google.com. If project is same at both console make sure you have add your SHA1 Key properly. Get SHA1 from Android studio.

Open Android Studio
Open your Project
Click on Gradle (From Right Side Panel, you will see Gradle Bar)
Click on Refresh (Click on Refresh from Gradle Bar, you will see List Gradle scripts of your Project)
Click on Your Project (Your Project Name form List (root))
Click on Tasks
Click on Android
Double Click on signingReport (You will get SHA1 and MD5 in Run Bar(Sometimes it will be in Gradle Console))
Select app module from module selection dropdown to run or debug your application   You also need to get google-services.json from firebase console and put into your project.

answered Mar 23 '18 at 13:33

Patrick R

5,704
1
18
25

1

Thank you for answer. At the step 8 I've got an SHA1 from Debug key, but I provided SHA1 code while registered app at google console from my primary key. Does it matter and how can i fix it? – max podgorny Mar 23 '18 at 13:46
Please use SHA1 generated from singingReport at step 8, and let us know if it works or not. – Patrick R Mar 26 '18 at 06:01
THANK YOU! It works! But how can I replace a debug key by my own (generated) key? – max podgorny Mar 26 '18 at 11:08
Perfect answer. Thank you! – Sam Chen May 27 '20 at 16:59
I don't understand step 9. What do I do with the signingReport output ? – Chris Neve Mar 05 '21 at 15:34

score 8 · Answer 2 · answered Dec 11 '19 at 22:41

I landed into the same problem and wasted hours. On digging deeper into OAuth and OpenId, I figured out the reason. We are doing a conceptual error here.

For android or any other platform (except web), you need to create at least two types of client id in the same project of google API console. These Client ID types are:

Web Application
Android

You can create them in any order. While creating Android type Client Id, you need to give package name and SHA1. While creating Web Application Id, you just need to give a name.

You don't need to do anything with any of these id's further until you want to verify the user at your backend. In other words, if you want your backend server to ask google server about this user's information, then only you would need Web Application Id. The conceptual flow is as follows:

First send Web Application Client Id from Android App to Google Sign-in Server as an additional option using requestIdToken(your_web_app_client_id).
You will get back a token in Android app upon user's sign in.
Send this token to your backend.
Now your backend can exchange this token with Google Servers to get user's information

Send this Web Appplication Client Id from Android App to backend server.

Use this Web Application Id if you want to verify user at your backend.

thx man i solved this problem, i send cliendID but android and must be clientID web application — papo, Oct 28 '20 at 05:30

score 4 · Answer 3 · answered Nov 13 '20 at 20:06

4

The answer for me was that you actually need to combine the two main answers given here:

Make sure that you created Google OAuth client ids for Android (one for Debug and one for release) and then assure that they have assigned the right SHA1 as described in the accepted answer.

Then you also need to create an OAuth client ID for Web and use that one for the actual SignIn:

GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
    .requestIdToken(WEB_CLIENT_ID)
    .requestEmail()
    .build();

answered Nov 13 '20 at 20:06

hugo der hungrige

11,164
8
52
80

Have you tried this in production? It works with debug, but when publishing to app store using release apk, it gives the error again – DIRTY DAVE Apr 16 '21 at 09:07
1

@DIRTYDAVE As far as I know, this should work. You can check the code here: https://github.com/johannesjo/super-productivity-android/blob/master/app/src/play/java/com/superproductivity/superproductivity/Google.java and download the app here: https://github.com/johannesjo/super-productivity/releases – hugo der hungrige Apr 16 '21 at 10:51
Thanks hugo, using the web application one is working for me in production. Google makes it so confusing I may have looked through 20+ questions on this GoogleSignIn issue... – DIRTY DAVE Apr 25 '21 at 12:09

Heroselohim · Answer 4 · 2020-07-14T14:25:13.910

Another source of this error is adding applicationIdSuffix to your Build Variants (Flavors) in the gradle file. If you had everything working and suddenly when adding flavors the Google Sign In broke, check this configuration variable.

The applicationIdSuffix parameter might require a unique certificate for each suffix. I simply removed it because I didn't need to deploy different products or releases yet. Also, you can set the same configuration for each flavor programmatically.

Configure certificates build types: Force to use same certificate to sign different "buildTypes" that are configured for a particular "productFlavor"?

score 2 · Answer 5 · answered Nov 06 '20 at 14:03

I've found another source of the problem.

In my case the keys were alright, but applicationId field in build.gradle script differed from app's package name.

Small research showed that applicationId field value takes some kind of "precedence" before app's package name conserning Google autentication.

After commenting applicationId line in build.gradle, app autenticates itself in Google by package name.

score 2 · Answer 6 · answered Nov 20 '20 at 17:59

I fixed this problem this way

 GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
                .requestIdToken(getString(R.string.AUTH_ID))
                .requestEmail()
                .build();

where my AUTH_ID is

score 1 · Answer 7 · answered May 16 '18 at 03:00

I would like to add Supplemental Information as to Why @Patrick R answer (above works/marked as correct). To execute your project/practice, Google Console needs to ID your app via SHA-1 key when its distributed on Google Play Market, However, when your are simply experimenting with Login confirmation and Proof Of Concept, then it associates the debug SHA-1 key (your app automatically generates this) for this exact purpose, keeping your testing and production changes modular.

score 1 · Answer 8 · answered Jul 18 '20 at 04:08

Add your debug.keystore's SHA1 and SHA256 fingerprint to your Firebase project.

Obtain the debug.keystore's fingerprints: Linux/Mac - keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore, Windows - keytool -list -v -alias androiddebugkey -keystore %USERPROFILE%\.android\debug.keystore
Add these fingerprint's to your Firebases project's Android app section: https://support.google.com/firebase/answer/9137403?hl=en

Vladyslav Ulianytskyi · Answer 9 · 2021-04-29T09:29:17.047

1

Option: then keep in mind that google also signs the app with the another certificate. So, you need to add the 2nd fingerprints as well. Otherwise, you will receive this error.

edited Apr 29 '21 at 09:29

answered Jul 28 '20 at 09:04

Vladyslav Ulianytskyi

1,015
17
14

1

This was my exact problem. I was going crazy thinking what the hell was wrong. – Nongthonbam Tonthoi Oct 26 '20 at 13:05

score 0 · Answer 10 · edited Aug 07 '20 at 22:42

0

Try adding .requestIdToken(getString(R.string.default_web_client_id)).

    GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
            .requestIdToken(getString(R.string.default_web_client_id)) //add this line
            .requestEmail()
            .build();

edited Aug 07 '20 at 22:42

TrampolineTales

731
3
12
27

answered Aug 07 '20 at 16:27

Jan Rozenbajgier

11
1
4

i have added all this but still i get this error i have added in firebase also – gulab patel Oct 04 '20 at 13:36
Did you update your google-services.json after adding SHA 1 to firebase? – Jan Rozenbajgier Oct 05 '20 at 14:14

score 0 · Answer 11 · answered Mar 04 '21 at 07:55

This Problem can be solved by using WebApplication ID and android Client ID

When ever you configure the project to generate id for android app , it generates 2 types of ids 1 Android 2 WebApplication ,

We need to use 2nd one and not the 1st one , it will be resolving your issue

score 0 · Answer 12 · answered Mar 14 '21 at 04:28

0

Had same issue. Code 10 in signed apk. I put all the four keys from Google Play Console (Setup -> App integrity -> Play App Signing) to Firebase project and pasted new Google-services.json in app folder in Android Studio and then after generating Signed Apk, Google sign in worked.

answered Mar 14 '21 at 04:28

Syed Umair

445
4
9

Thanks @Syed Umair. This solution works for me – padlanau Mar 29 '21 at 09:13

score 0 · Answer 13 · answered May 06 '21 at 09:18

0

I paste the release keystore sha1 to google console, but forget add debug config !!

answered May 06 '21 at 09:18

hoot

1,105
13
14

Google SignIn API Exception 10

13 Answers13

Linked