Google Sign in but result code is 0

Question

I want to create a Google sign for my app but my result code from onActivityResult() is 0

In my onCreate() Method I start the function startSignInIntent() like this:

protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        //some other stuff
        view.loadUrl(myURL);
        startSignInIntent();
}

This is the startSignInIntent()

private void startSignInIntent() {
        GoogleSignInClient signInClient = GoogleSignIn.getClient(this,
                GoogleSignInOptions.DEFAULT_SIGN_IN);
        Intent intent = signInClient.getSignInIntent();
        startActivityForResult(intent, RC_SIGN_IN);
    }

This is the onActivityResult()

protected void onActivityResult(int requestCode, int resultCode, Intent data) {
        super.onActivityResult(requestCode, resultCode, data);
        Log.d(TAG, "data : " + resultCode + " | " + data  + " || " + RC_SIGN_IN + " ||| " + requestCode);
        if (requestCode == RC_SIGN_IN) {
            GoogleSignInResult result = Auth.GoogleSignInApi.getSignInResultFromIntent(data);
            if (result.isSuccess()) {
                // The signed in account is stored in the result.
                GoogleSignInAccount signedInAccount = result.getSignInAccount();
            } else {
                String message = result.getStatus().getStatusMessage();
                if (message == null || message.isEmpty()) {
                    Toast.makeText(this, "Login failed", Toast.LENGTH_LONG).show();
                }
                new AlertDialog.Builder(this).setMessage(message)
                        .setNeutralButton(android.R.string.ok, null).show();
            }
        }

This the result of the log in the function onActivityResult()

0 | Intent { (has extras) } || 2 ||| 2

After I select an account of the the pop-up where I can choose my account. I get this screen with ok but when I have that the login already failed. See photo:

Try checking if you have the correct OAuth key properly configured for your app. According to this related [SO post](https://stackoverflow.com/a/45211254/5995040), the OP noticed that the Auth key is also associated with other project that create the issue. Also you can check the following implementation of [Try Sign-In for Android](https://developers.google.com/identity/sign-in/android/start), for code implementation. Hope this helps. — Mr.Rebot, Nov 18 '17 at 20:47

score 18 · Answer 1 · answered Mar 29 '18 at 11:41

18

I've had the same bug, requestCode was always 0 (RESULT_CANCELED).

Decision was to enable google sign in in firebase console.

Firebase console -> Your project -> Authentication -> Providers -> Google -> and switch it on.

In my case link was like this

https://console.firebase.google.com/u/0/project/{PROJECT NAME}/authentication/providers

answered Mar 29 '18 at 11:41

Eugene P.

926
9
12

This is probably true if you are using the firebase analytics? I was getting the error so I followed the steps and along the way had to make a couple of changes to the project. I think the change that mattered was changing `applicationId` to match with the one which I had registered with Google developer console. The `package` in AndroidManifest.xml and `applicationId` are now the same in my app and without the firebase changes, I get -1 as the return value for the signIn! – Chetan Narsude Jul 09 '20 at 11:47
This was 2 years ago, so maybe something has been changed. – Eugene P. Jul 23 '20 at 14:03
@EugeneP. nothing has changed. Enabling Google signin made it works. -.- – Jumpa Aug 12 '20 at 10:53

Mr.Rebot · Accepted Answer · 2017-11-19T15:38:41.927

Try checking if you have the correct OAuth key properly configured for your app. According to this related SO post, the OP noticed that the Auth key is also associated with other project that create the issue.

Also you can check the following implementation of Try Sign-In for Android, for code implementation:

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

    // 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.
        Task<GoogleSignInAccount> task = GoogleSignIn.getSignedInAccountFromIntent(data);
        handleSignInResult(task);
    }
}

Also, some additional information provided by OP, you need to make sure you have signed the APK when you are testing it. See the documentation about Sign Your App for detailed information about it.

Hope this helps.

Add this also to your solution that you need to sign the apk when you test. Otherwise it will not work — Steven, Nov 19 '17 at 14:09

score 4 · Answer 3 · answered Dec 20 '20 at 14:50

4

Make sure to set the publishing status of your OAuth consent screen to In Production status instead of Testing status.

answered Dec 20 '20 at 14:50

Abel Stuker

89
1
3

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

3

I faced the same problem with Android Emulator. It turns out that the emulator was disconnected from the Internet that why firebase it was throwing above mentioned error.

answered Nov 02 '19 at 13:20

Pratap Vhatkar

691
10
21

or on a real device if it's not online ... – lenooh Nov 20 '19 at 14:23

score 2 · Answer 5 · answered Nov 14 '19 at 00:13

I wanted to share my experience even though it is not applicable to the original case. My search landed here because I had the same problem - startActivityForResult returns instantly with resultCode = 0.

My cause was the wrong package name. I have an app with a few variants each of which has a different package name. Google Sign-In requires that the Android app's package name matches one of the Google API console's Android projects' package name. I set up a project for one variant, but did not for others. Once I created a project for the Google API Console, the sign-in started to work flawlessly.

I forgot that I recently added multiple build types and flavors, each with their own applicationIdSuffix. After creating OAuth-Client-IDs for all of them it works fine again. Thanks. — m-rm, Jan 17 '20 at 14:44

score 1 · Answer 6 · answered Nov 14 '20 at 00:28

In my case, I had forgotten to add the project ID to AndroidManifest.xml. Thus:

<meta-data android:name="com.google.android.gms.games.APP_ID"
           android:value="@string/app_id" />

and in the folder res/values create a file ids.xml and set the ID of the project

<string name="app_id" translatable="false">numberOfProject</string>

score 0 · Answer 7 · answered May 12 '19 at 00:21

I had this going on specifically on android jellybean and it turned out to be that if the signin activity launch mode I was using was not standard or singletop in the manifest the onActivityResult() would return immediately without actually waiting for the result.

 <activity
       android:name=".SignInActivity"
        android:excludeFromRecents="true"
        android:exported="true"
        android:launchMode="singleTop"
        android:permission="com.google.firebase.auth.api.gms.permission.LAUNCH_FEDERATED_SIGN_IN"
        tools:replace="android:launchMode"/>

score 0 · Answer 8 · edited Oct 08 '20 at 23:42

Just got it fixed... I was trying to clean up some OAuth IDs in the Credentials but removed a wrong one.

visit Start Integrating Google Sign-In into Your Android App
click Configure a project
select your project / create one
choose Android then fill in your package name & SHA-1
copy and use the (Web application) client ID

I found that this setup will create 2 OAuth 2.0 Client IDs:

OAuth client (Type: Android)
Web client (Auto-created for Google Sign-in) (Type: Web Application) <- the one I missed

Google Sign in but result code is 0

8 Answers8

Linked