Flutter and google_sign_in plugin: PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null)

I run into the same issue just now. This might happens if you are running on debug and you did not register a SHA fingerprint in firebase. I solved it by generating a debug.keystore by running:
keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore

and registering it inside the app on Firebase. Don't forget to download the new google-services.json after that.

See also this.

Edit If you are not able to use authenticate in release mode try the following:

-Add the SHA certificate fingerprints of the release key.

keytool -exportcert -list -v \ -alias <your-key-name> -keystore <path-to-production-keystore>

For more details on that see here on the section "get release certificate" https://developers.google.com/android/guides/client-auth

If your authentication is still not working, probably it is because you downloaded the app from Playstore and you enabled the "App Signing by Google Play Feature" Then for this case, go to play store publish console and go to app signing under release management. There you will find the SHA certificate fingerprint to register in Firebase console.

Final step: If it still not working, double check that you have put the right fingerprints with cd android then ./gradlew signingReport (check Variant: debug, release ). It should work now. But if not, try to run terminal run the command flutter clean.

I spent ages trying to fix this.

1. Open grade.properties This file is found under: {{YOUR PROJECT}}/android/gradle.properties

2. Add the following argument to 'org.gradle.jvmargs' as shown in the screenshot.

-XX:MaxHeapSize=256m -Xmx256m

3. Right click on 'gradlew' and go to 'Open in Terminal' This file is found under {{YOUR PROJECT}}/android/gradlew

4. Type in the following command.

gradlew signingReport

If did not work first try second command:

./gradlew signingReport

5. Wait for the compilation to finish and your SHA keys should be printed out for you.

Use these keys to authenticate your app in https://console.firebase.google.com/

Open the Firebase console and click on the settings icon.

You will see the list of the apps connected to your Firebase project

For Android

1. Open terminal inside your flutter project
2. cd android
3. ./gradlew signingReport or gradlew signingReport
4. Paste your SHA1 key
5. Download and replace the google-services.json
6. flutter clean

IOS:

1. Configure your Firebase project
2. Select IOS
3. Enter your Bundle ID
4. Download credetials
5. Download and replace GoogleService-info.plist

Add this to your info.plist

<key>CFBundleURLTypes</key>
<array>
    <dict>
        <key>CFBundleTypeRole</key>
        <string>Editor</string>
        <key>CFBundleURLSchemes</key>
        <array>
            <string>**INSERT HERE YOUR RESERVED_CLIENT_ID FROM GoogleService-Info.plist**</string>
        </array>
    </dict>
</array>

The following solution works in flutter project:

Step 1: Generate SHA1 and SHA256 keys.
Step 2: Add both the SHA1 and SHA256 to firebase. (in you app settings)
Step 3: Download google-services.json to android/app in your project folder.
Step 4: In your terminal run the command flutter clean .
Step 5: Run your flutter app.

For more information visit:
https://developers.google.com/android/guides/client-auth
https://firebase.google.com/docs/flutter/setup

For me I didn't need to add extra SHAs, I realized I didn't enable the Google Sign-in method in the Authentication tab in Firebase console

When I came across this problem, I tried all other solutions described in this post. None of these worked. Eventually I figured it out: In my situation I had to make sure to have my "support email" set.

Additional steps you might have to take in order for google_sign_in to work:

• Link GooglePlay with Firebase [(https://github.com/flutter/flutter/issues/27599)

• If you could run Google Sign In during debug but NOT in release, there is a high chance that you did not add your release key's SHA1 and SHA256 to firebase. To get the release key's SHAs, use keytool -list -v -keystore ~/key.jks -alias key

You should end up with total of at least 6 SHA credentials: 2 from the debug key, 2 from Google Play linking, and 2 from the release key. Note that you do not need to redownload the google-services.json file after adding the release SHA credentials to firebase.

• Add GooglePlay Proguard rules (https://github.com/flutter/flutter/issues/19102)

# Flutter Wrapper
-keep class io.flutter.app.** { *; }
-keep class io.flutter.plugin.**  { *; }
-keep class io.flutter.util.**  { *; }
-keep class io.flutter.view.**  { *; }
-keep class io.flutter.**  { *; }
-keep class io.flutter.plugins.**  { *; }

# GooglePlay Services
-keep class com.google.android.gms.** { *; }
-dontwarn com.google.android.gms.**
-keep class com.google.common.** { *; }
-dontwarn com.google.common.**

If your released app is not working properly, and you are using Google Play Signing, Copy the SHA from your play store account, the one from your local key will not work

I found a solution for the error com.google.android.gms.common.api.ApiException: 10: I solved it by adding more keys to the firebase. initially I thought it was stupid and useless, then in the end it turned out to be the solution (I added up to 10 SHA, don't worry if that's a lot).

1. Where did I find all these keys?

I found all these keys by entering the android folder and typing the command ./gradlew signingReport (I use linux, it also works on mac. For windows the command is gradlew signingReport)

2. After that?

After that, he printed out a very long list of keys in my terminal, and I took all the ones that were different, that were at the top of the list.

Note: you will get all the keys (both debug and release) of each package of the app, but rest assured that all those of the packages are the same and only for debugging (so you will have to take these same keys only once)

3. Finally

Once you have all the app keys, go to your project's Firebase settings, scroll down and add any keys you found. After that, you will need to download the google-services.json file again and run a flutter clean in your project's local folder on your computer.

Now you can build your app and see if it works!

I hope this could help someone.

The answer that given early are right. None of them are false. But if you still face the error PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null). One thing that your should check is your OAuth 2.0 Client IDs

1. Go to : https://console.cloud.google.com/apis/credentials
2. Select your project on the top left screen
3. Create Client ID base on your platform (iOS or Android)
4. Just follow the next steps

Once you successfully generate the client ID, then your application will works as expected.

--- Note ---

But first, make sure you have regitered your SHA-1, package id email support and has been download the google service json from your firebase console project.

"Flutter clean" its the piece that everybody is missing after register the SHA1 in Firebase Console!

You have missed configuration step enable google login on firebase.

Google sign-in is automatically configured on your connected iOS and web apps. To set up Google sign-in for your Android apps, you need to add the SHA1 fingerprint for each app on your Project Settings.

✅ Just complete these enough steps below

1. Enable Google Auth Method
2. Configure certificate fingerprints in your current project at project-level setting. How to Generate certificate.
3. Select email for Project support email
4. Download google-service.json into your project.
5. Run flutter clean
6. start flutter run

make sure you have added

 dependencies {
    classpath 'com.google.gms:google-services:4.2.0'
}

in android/build.gradle and

apply plugin: 'com.google.gms.google-services'

in android/app/build.gradle. Also, make sure applicationId in android/app/build.gradle is the same as your package name in AndroidManifest.xml(You may forget to change applicationId after changing package name sometimes). This applicatioonId or package name in manifest file should be the name of your android package name in firebase app.

One reason that you might be experiencing this error is if you did not fill out google's OAuth consent form. This is a new change to Firebase.

Here are the steps you need to follow to fill out the consent form for your app:

1. Navigate to the google api console (currently at https://console.developers.google.com), make sure you are logged into your account which your firebase project is created under.
2. Select your project from the "select a project" dropdown in top left of the developer console.
3. In the left hand pane travel to "credentials" and then switch to the "OAuth consent screen".
4. Under "Application name" enter your application's public name
5. Under "Application logo" upload a local image file of your application
6. Under "Support email" enter the same support email listed in your firebase application.

7. Scroll down and fill out the "Application Homepage Link", "Application Privacy Policy Link", and "Application Terms of Service Link" by adding http:// before the authorized domain which your firebase app lives at.

8. Click Save

These steps worked for me! While the link may not still exist, I'd like to reference the source of this solution here

For platform exception 10, try this:

1. Generate a new SHA1 fingerprint on your machine,
2. Go to your firebase android app setting in Firebase Console
3. Click on add new fingerprint in your android app settings
4. Paste the new SHA1 fingerprint into the field
5. Generate a new json config file
6. Replace the config file in android directory
7. Run flutter clean
8. Run your project

I tried all of the above answers and none worked. I'm putting my solution here in case someone runs into an edge case like mine:

1. Mine didn't work with the above answers because I'm installing the app via Firebase App Tester (Firebase Distribution) and it resigned the app with entirely new test certificates, not the usual debug or release certificates you can get from Android Studio
2. To solve it, go to Firebase App Distribution from Firebase Console and copy the test certificates SHA-1 and SHA-256
3. Enter these new certificates in Firebase Project Settings

In my case, none of the answers solved the problem. After some thinking, I realized that sometime ago I have changed the package name of my application. If it is your case, you should simply create another application inside your Firebase project with your new package name and download google-services.json file again.

This happened to me also when I have reinstalled my OS. Just run ./gradlew signingReportand copy the SHA-1 and SHA-256 into Firebase config "add fingerprint"

If your implementation works everywhere but not on Android, make sure that you use the correct WEB clientId supplied to GoogleProvider(clientId: clientId) when using firebase_ui_auth package.

I repeat: Use WEB clientId to make Google SignIn work on Android.

This is completely counterintuitive and not documented anywhere. It took me three days of trial and error until I finally found this comment.

I had the same issue on android tried all above but not fixed. In my case issue was very simple. In my project i had already add google-service.json file and in my code pass clientId too

clientId is optional param required for IOs, so its least to error in Android.

check this too

Happy coding :)

This might seem silly, but that just happened to me now (after having some experience working with firebase in the past). I noticed that I did not enable Google authentication. Make sure you do that, as you might still see the login prompt (showing you your phone's google users, without it being enabled).

This answer has already more 30 answer but this is more COMPLETE STEP BY STEP APPROACH to solve this bug.

1. Most likely you do not have debug.keystore in your C/User/.android directory. To generate one, do the following

$ keytool -genkey -v -keystore debug.keystore -storepass android -alias androiddebugkey -keypass android -keyalg RSA -keysize 2048 -validity 10000

use organization name Android country code US and name Android Debug

2. when you have done so, navigate to your android flutter directory where gradlew is located and do the following

./gradlew signingReport

3. You will have list of SHA1 SHA256 keys. copy both keys that is named debug.keystore to your flutter project firebase project settings (where you download google-services.json)

Flutter clean and rebuild your project.

In my case the problem was I didn't add signinConfigs for debug in the android/app/build.gradle. I only added for release so the app wasn't working as I tested it.

android {
    ...

    signingConfigs {
        release {
            keyAlias keystoreProperties['keyAlias']
            keyPassword keystoreProperties['keyPassword']
            storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
            storePassword keystoreProperties['storePassword']
        }
        # It started working when I added the following debug section.
        debug {
            keyAlias keystoreProperties['keyAlias']
            keyPassword keystoreProperties['keyPassword']
            storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
            storePassword keystoreProperties['storePassword']
        }
    }
    buildTypes {
        release {
            signingConfig signingConfigs.release
        }
    }
}

I got this style of "referencing the keystore from the app" from https://docs.flutter.dev/deployment/android#reference-the-keystore-from-the-app.

You should generate SHA-1 and SHA-256 for each pc that you used. And add them all to firebase project settings.

And you should fill the form in OAuth Consent tab.

If it previously worked but now are using a different PC, you'll need to add new SHA-1/SHA-256 fingerprints generated by that PC to your project in Firebase. A good step-by-step example on doing that: https://stackoverflow.com/a/56091158/5365164

In my case it was a silly mistake,make sure that your applicationId in firebase like : 'com.example.appname' matches exactly with the applicationId in your app/src/build.gradle file,under the defaultConfig{}.No spelling errors,no upper case,lower case letter conflicts.In my case one letter was upper case which caused all the problems.

I know this issue has many replies already but I haven't seen this one yet. I solved ApiException: 10 by cleaning up!

1. Removed unused OAuth 2.0 Client IDs from https://console.cloud.google.com/apis/credentials
2. Removed unused fingerprints from the Firebase console.
3. Download google-services.json again

You need to add your SHA-1 and SHA-256 to your Firebase project. If you've published your app using Play App Signing, a requirement when using Android App Bundle, you can get your SHA-1 from the Google Play Console on the Release > Setup > App Integrity page.

I faced a similar problem. but I solved it by taking a simple step.

First, let me tell you how the problem happened with my project:

I have linked my Flutter app to the Google Cloud Console to use Google Sign-In without Firebase. And it was working. Later, I linked the app (the Flutter app) to Firebase to use phone authentication. After this, when I tried to log in with Google Sign In, this error was thrown: "PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10:, null, null)".

The reason was, When I call this method:

final response = await _googleSignIn.signIn();

The request was sent to Firebase, not Google Cloud Console. So, I tried this solution, and the error was solved:

1. The solution is to just open your "google_services.json" file and delete the "client_id" from the this code in google_services.json file.

 "oauth_client": [         {     "client_id": "872887541893-6rib4t0mk07gu1l80emetda6o65e2m76.apps.googleusercontent.com",           "client_type": 3         }       ], 2. Run this command on your app's VSC terminal.    2.1.flutter clean 2.2. flutter pub get then run your app. it worked for me. Let me know if you have an issue with the above explanation.

Got the same issue. I checked the signingReport and found that the release SHA1 and SHA256 were different from others. I added these values in firebase and re-downloaded the google-services.json. This solved the issue.

Also, run flutter clean before building apk.