Error: Status{statusCode=DEVELOPER_ERROR, resolution=null}

Question

I am usign gplus sign in, and getting this error at time I am in onActivityResult....

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

    if (requestCode == 0) {
        GoogleSignInResult result = Auth.GoogleSignInApi.getSignInResultFromIntent(data);
        if (result.isSuccess()) {

            GoogleSignInAccount acct = result.getSignInAccount();
//                Log.d("Result","details"+ acct.getDisplayName() + acct.getEmail());

            mEmail = acct.getEmail();
            String mFullName = acct.getDisplayName();
            String mGoogleplusId = acct.getId();


            SocialUser user = new SocialUser();
            user.setType("googleplus");

            user.setEmail(mEmail);
            user.setFullname(mFullName);
            user.setId(mGoogleplusId + "");
            loginParams.put("email_id", mEmail);
            loginParams.put("googlePlusId", mGoogleplusId);
            loginParams.put("full_name", mFullName);
            loginParams.put("registrationType", "googleplus");
            SignUpService(user);


        } else {
            Toast.makeText(CustomerLogIn.this, "Unable to fetch data, Proceed manually", Toast.LENGTH_SHORT).show();
        }
    }
}

And I am calling for gplus login on button click. On clcking button following code is executed....

 GoogleSignInOptions googleSignInOptions = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
            .requestEmail()
            .build();
    mGoogleApiClient = new GoogleApiClient.Builder(CustomerLogIn.this)

            .addApi(Auth.GOOGLE_SIGN_IN_API, googleSignInOptions)
            .build();


    Intent signInIntent = Auth.GoogleSignInApi.getSignInIntent(mGoogleApiClient);
    startActivityForResult(signInIntent, 0);

And I am geetng this error...

Status{statusCode=DEVELOPER_ERROR, resolution=null}

on this line....

GoogleSignInResult result = Auth.GoogleSignInApi.getSignInResultFromIntent(data);

Please suggest the solution.

The application is misconfigured. Check google api configuration. — 1'hafs, May 17 '16 at 10:52
I don't use firebase. See my solution here: https://stackoverflow.com/a/46828895/1160216 — Mike Miller, Oct 19 '17 at 11:34
@MiguelSilva is it just a web client id ? or do I need to fill redirect uri ? — John Stuart, Sep 18 '21 at 18:38

score 237 · Accepted Answer · edited Feb 25 '20 at 15:27

237

You need to add your SHA1 key to firebase console configuration. You can do it in this way:

Firebase console ( https://console.firebase.google.com ) -> your project -> configuration -> scroll to

You can find your SHA1 key running "Signing report" from Android Studio:

Then, look the "run tab" and click the button:

I think it's the easier way. Hope this help.

edited Feb 25 '20 at 15:27

Vadim Kotov

8,084
8
48
62

answered Jun 12 '17 at 18:40

SolArabehety

8,467
5
38
42

1

here is the easiest way to get release SHA-1 from google developer console: https://stackoverflow.com/a/50124038/4923891 – Eren May 01 '18 at 21:26
1

I had problem to understand where to put that SHA key in Firebase Console. Finally found it. Open Project Settings > Scroll Down, Add Fingerprint, Put your SHA key there > Download new google-services.json and place it android-app\app – paakjis Aug 09 '18 at 10:52
1

Note! Even though firebase console has a space for SHA-256 key hash, you MUST enter the SHA-1 key. The SHA-256 will still give you errors – f.khantsis Feb 09 '19 at 23:21
Helpful. Thanks! – Pooja Mar 15 '20 at 05:53
I have this issue too, but only on release version of the Android app. On debug it seems to work fine... How come? – android developer Feb 02 '23 at 14:48

score 32 · Answer 2 · edited Mar 27 '18 at 15:01

32

Probably you created the configuration file using the SHA1 of your production token, use the androiddebugkey alias to gather the SHA1 corresponding to the debug version of your app and copy the configuration file to the 'app' directory, you should have both configuration files (one for debug purposes and another for production environment).

Based on the walkthrough published in https://developers.google.com/identity/sign-in/android/start

edited Mar 27 '18 at 15:01

CopsOnRoad

237,138
77
654
440

answered Jun 01 '16 at 17:34

Mario

421
3
4

7

My error was fixed when I switched to the Web Client credentials instead of the Android Client for the OAuth 2.0 client ID's. The wording still confuses me as I am developing an Android app which talks to a web server... but the error is gone at least – Burrito Aug 13 '17 at 00:57

score 14 · Answer 3 · answered Aug 07 '17 at 17:29

14

The way I fixed it was by picking up the key corresponding to the highlighted text. Due to the confusing usage of the word 'server' in Firebase's documentation page I was picking up the Server key . Which was the reason for the problem.

You can find the key here.

answered Aug 07 '17 at 17:29

4127157

1,438
2
15
28

Thanks! Worked in my case. I think it somehow connected with using own backend server (and calling for "requestServerAuthCode" in GoogleSignIn) – ITurchenko Jun 21 '18 at 14:34

Udit Kapahi · Answer 4 · 2016-09-19T09:26:27.760

12

I had the same issue and I got it working by doing these steps:

1.Add DEBUG_KEYSTORE SHA1 fingerprint to the firebase project. use the following command(MAC/LINUX)

  keytool -exportcert -list -v \-alias androiddebugkey -keystore ~/.android/debug.keystore

2.Now Generate a signed apk of your project. The process includes generating a keystore for your app's release version.

  Copy the path of the newly generated .jks file.

3.Now generate RELEASE_KEYSTORE SHA1 fingerprint using the following command

  keytool -list -v -keystore FULL_PATH_TOJKS_FILE -alias ALIAS_NAME

4.Copy the new SHA1 from the output and add it as another SHA1 fingerprint in your firebase application console.

Now you are good to go! ---- Hope! it helps.

edited Sep 19 '16 at 09:26

answered Aug 22 '16 at 12:15

Udit Kapahi

2,277
1
27
25

that released sha1 only am placing then also getting this error,generate google_services.xml for google sign in,analytics and gcm,single file – Harsha Sep 28 '16 at 11:39
make sure that your sha1 is of the 'release' version of the app not the 'debug' version – Udit Kapahi Sep 29 '16 at 10:01
Ha Yes am generating signed apk and published in appstore also,that jks and keystore passwords only am using – Harsha Sep 29 '16 at 10:15
my open ssl is openssl-0.9.8k_WIN32 am using previos for development one – Harsha Sep 29 '16 at 10:17
`keytool` **requires a password**: "android" – Guglie Jul 15 '20 at 16:33

score 5 · Answer 5 · answered Aug 21 '16 at 06:21

5

I was having the same problem, how I solved it is that I had different applicationId in my gradle file than the package name in my manifest file. And I used to applicationId to create the json file. I had to change my package name to what my applicationId was and that fixed it for me.

answered Aug 21 '16 at 06:21

Renegade

642
1
10
19

1

i always thought the package in the Manifest was overridden by the ApplicationId defined in gradle. That's not the case? – Flo We Nov 02 '16 at 08:47

score 5 · Answer 6 · answered May 31 '18 at 08:10

It's an old question, but I have been stuck with error 10 (DEVELOPER_ERROR) lately, because I was using the Android client ID, I created in the google developer console.

The solution for me was to use the Android credentials in google developer console only to indicate the SHA key of my apk and to use the client ID of the Web application (!) credentials from the google developer console in my cordova application.

config.xml:

<plugin name="cordova-plugin-googleplus" spec="^5.3.0">
    <variable name="REVERSED_CLIENT_ID" value="com.googleusercontent.apps.[web-application-client-id]" />
    <variable name="WEB_APPLICATION_CLIENT_ID" value="[web-application-client-id].apps.googleusercontent.com" />
</plugin>

code:

window.plugins.googleplus.login(
    {
       'webClientId': '[web-application-client-id].apps.googleusercontent.com'
    }, 
    ...

I don't use firebase.

Thank you very much, it saved me a lot of time. Indeed using auto-generated web `client id` solved the DEVELOPER_ERROR issue. Although for me it doesn't make sense and it's not obvious that different client id should be used. — Myroslav, Jan 16 '20 at 13:45

Jagjit Singh · Answer 7 · 2020-01-04T06:49:32.720

4

Please Put correct json file in root of the android project
For more Refer here: https://coderzpassion.com/android-working-latest-google-plus-login-api/

edited Jan 04 '20 at 06:49

answered May 17 '16 at 10:26

Jagjit Singh

1,909
1
14
19

Is it compulsory to add that json, we use to do without it before? – Gurvinder Singh May 17 '16 at 11:59
I put the right file with right configuration, still there is error – Bibaswann Bandyopadhyay May 27 '16 at 11:44
kya baat a ...apne bande da answer mil gya – karanatwal.github.io Jul 10 '23 at 18:00

score 4 · Answer 8 · answered Nov 14 '17 at 13:58

Alternatively to the answers provided here, you can use Android Studio's Firebase Assistant to automatically add your SHA-1 to your project with the click of some buttons.

In Android Studio, go to Tools > Firebase > Select 'Authentication' and click the link that says 'Email and password authentication'.

This will bring you a little tutorial on how to integrate Authentication to your project, but since you've probably done all that, just click 'Connect to Firebase' and you're done.

score 4 · Answer 9 · answered Jun 27 '18 at 16:57

You might have generated and added wrong SHA1 key. Use following steps to generate SHA1 key in Android studio:

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))

Now add this SHA1 key in your firebase android project.

score 1 · Answer 10 · answered Oct 10 '17 at 05:00

The error is caused because the SHA-1 checksum of the debug or release key is not included in the firebase/google console.

First generate key using following command:

keytool -list -v -keystore KEYSTORE_PATH -alias ALIAS_NAME

Then copy the SHA-1 checksum and go to:

Firebase Console > Your project > Settings of the app > Add Fingerprint

score 1 · Answer 11 · answered Sep 09 '18 at 06:57

For me it was working when I first implemented it, but stopped after a few days of development, with the mentioned error message.

I've solved the issue with these steps:

I have added the sha-256 fingerprint on top of the sha-1 fingerprint that I already had in the firebase console. (Not sure if this step is required)
I have downloaded google-services.json file again and replaced the old file.
re-installed the app

and it worked

score 1 · Answer 12 · answered Jan 18 '22 at 19:00

1

Check below steps

Make sure you use correct SHA keys
Use web client id, not android client id while requesting id token

answered Jan 18 '22 at 19:00

Parth Desai

196
2
10

score 0 · Answer 13 · answered Oct 20 '16 at 07:21

0

I came across this error in my firebase app. It was fixed when I added therequestIdToken(activity.getString(R.string.default_web_client_id)) part below.

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

    apiClient = new GoogleApiClient.Builder(activity)
        .addConnectionCallbacks(this)
        .enableAutoManage(activity, this)
        .addApi(Auth.GOOGLE_SIGN_IN_API, gso)
        .build();

    Intent signInIntent = Auth.GoogleSignInApi.getSignInIntent(apiClient);
    activity.startActivityForResult(signInIntent, RC_GOOGLE_SIGN_IN);

answered Oct 20 '16 at 07:21

Dan Brough

2,745
1
24
24

what is default_web_client_id? from where I can get it? – Ayman Al-Absi Nov 05 '16 at 19:07
@AymanAl-Absi Have you setup your project properly for google services? see: https://developers.google.com/android/guides/google-services-plugin – Dan Brough Nov 05 '16 at 22:11
1

@AymanAl-Absi you also get the "default_web_client_id" from your google-service.json file in this file you can see Client_ID tag in that tag you copy only that text (client_ID) <[Client_ID].app.etc> . – Prince Dholakiya Jul 11 '18 at 10:03

score 0 · Answer 14 · answered Nov 05 '16 at 20:08

0

I got this error when i updated my json config file with a new google account.

Uninstalling the application manually and reinstalling the app worked for me.

answered Nov 05 '16 at 20:08

sanath_p

2,198
2
26
22

score 0 · Answer 15 · answered Jan 21 '18 at 05:41

0

For anyone releasing an app, you need a special fingerprint from your keystore file. No wonder why I was getting this error just for the release version. How to obtain Signing certificate fingerprint (SHA1) for OAuth 2.0 on Android?

answered Jan 21 '18 at 05:41

Juan Mendez

2,658
1
27
23

score 0 · Answer 16 · answered May 07 '18 at 16:19

0

Ensure you enable Google Sign-In in under Authentication in the Firebase console.

answered May 07 '18 at 16:19

hellowill89

1,538
2
15
26

score 0 · Answer 17 · answered Sep 18 '19 at 13:59

0

I solved my problem by use right server_client_id in this line :

String serverClientId = getString(R.string.server_client_id);

I used the wrong code.

answered Sep 18 '19 at 13:59

The MJ

453
7
17

score 0 · Answer 18 · answered Jun 22 '20 at 06:08

Some Services like google login require SHA1 fingerprint to be added to your firebase console.

I missed adding SHA fingerprint in firebase console. You can do so by going in FireBase Console > project setting > Add fingerprint option.

You can generate SHA1 Fingerprint by a very easy way https://www.youtube.com/watch?v=FczARQ244GE

After that I was doing one more mistake

After generationg SHA1 key fom above method. I copied the wrong invalid SHA1 key which was an expired one. So make sure the SHA1 key that you are copying from above way output is a valid one (Check the valid untill value as well of SHA1 Key)

Also make sure that the package name(x.y.z) that you have added in firebase is same as used in your android code.

Also make sure to use correct AppID

Albert Aleksieiev · Answer 19 · 2020-06-28T15:19:03.297

0

After long invistigation I have found a solution. Actually this error Error: Status{statusCode=DEVELOPER_ERROR, resolution=null} points to incorrect SHA-1 OR Incorrect package name OR something else?. In my case, I add debug keyword to end of my package name com.sample.app => com.sample.app.debug

edited Jun 28 '20 at 15:19

answered Jun 28 '20 at 15:12

Albert Aleksieiev

107
8

In my project package name is correct and same as in google service json. And I think SHA-1 not needed in release key – Kalpana Aneyrao May 25 '21 at 11:08

score 0 · Answer 20 · answered Aug 17 '20 at 07:26

I struggled with this issue because I made a copy of my application with changing the package name. I add a new project for it at Firebase. My mistake was that I forgot to change the server's client ID to the one in the new Firebase project.

more details under authintication with Firebase sectoin here

score 0 · Answer 21 · answered Feb 16 '21 at 13:53

When you let Google manage your app signing, you can find the SHA-1 key in the Google Play console. On the sidebar menu look for 'Configuration -> App integrity'. Here you will find the SHA-1 key for the signed app.

You also see the SHA-1 key for the signed app you've uploaded to the store.

score 0 · Answer 22 · edited Mar 07 '21 at 11:19

0

don't forget to add release finger print. the former answers tell just add debug finger print which your problem just solve when you run your app in debug mode. if you release your app you can see that your problem is still remain . then make sure you added release finger print too .

edited Mar 07 '21 at 11:19

Dharman

30,962
25
85
135

answered Mar 07 '21 at 11:13

Mosayeb Masoumi

481
4
10

score 0 · Answer 23 · answered May 26 '21 at 13:19

0

If you're running into this issue with a released version (production):

Go to the Google Play console and copy SHA-1 key from Release -> Setup -> App Integrity

answered May 26 '21 at 13:19

Jeroen van Dijk

459
1
4
3

score 0 · Answer 24 · answered Dec 24 '21 at 14:30

0

This also might happen if you are working with app versions deployed from "Internal App Sharing" There is yet another certificate generated for you, and you'll need to registered it's SHA-1 fingerprint on Firebase or GCP too

answered Dec 24 '21 at 14:30

Mardann

1,953
1
16
23

score 0 · Answer 25 · answered Sep 27 '22 at 05:28

with new android updates, this has started happening on a lot of my projects. The fix that worked for me was to define signconfig for both debug and release version in the gradle file and use it in build types.

In one of my project release build was working fine but dev build was facing this error.

signingConfigs {
    debug {
        storeFile file('/Users/user/.android/debug.keystore')
        storePassword 'android'
        keyPassword 'android'
        keyAlias 'AndroidDebugKey'
    }
    release {
        storeFile file('/Users/user/Development/your_key')
        storePassword 'your_pass'
        keyAlias 'your_alias'
        keyPassword 'your_pass'
    }
}

buildTypes {
    release {
        minifyEnabled true
        debuggable false
        signingConfig signingConfigs.release
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
    debug {
        minifyEnabled false
        debuggable true
        signingConfig signingConfigs.debug
    }
}

hey thanks for the lead. but it doesn't help in my case. Do you think adding the sha-1 key in the console will solve the issue? @aamitarya — Anish Kumar, Sep 29 '22 at 11:10
Yes, you will definitely have to add sha-1 key in the firebase console for sure. This solution that I have added is on top of it. — aamitarya, Oct 04 '22 at 13:44

score 0 · Answer 26 · answered Apr 16 '23 at 06:14

if you are using expo (managed workflow) and eas, you may not have a debug keystore file, so you will receive this error when running android simulator from the terminal.

Apparently, I had everything setup correctly, but I needed to make a dev build:

eas build --platform android --profile development --local

then I needed to drag the .apk file to my simulator to test that it worked.

Error: Status{statusCode=DEVELOPER_ERROR, resolution=null}

26 Answers26

Linked

Related