Tried all available solutions on the internet but still getting same error, also cross Checked SHA1 key. Used both methods Firebase and Google Developer console but all in vain.
I have face this issue,
For me I am using react-native-google-signin with firebase.
My problem was SHA certificate fingerprints on firebase console is different with my project keystore.
U can check it by run this command to make sure your SHA on firebase and keystore is same.
keytool -list -v -keystore ~/.android/debug.keystore
This is often caused by no/invalid App Signature. You most likely use bare workflow, since you're getting this error, because expo does this for you when you build the app. To achieve the same in bare workflow
Drop your android folder in Android Studio
In Upper toolbar click Build >> Generate Signed APK
Choose APK from given options.
Type in your KeyStore informations.
After building an app, you must be able to use google sign in.
I had created a sign in page in flutter using phone Authentication. In which i am getting the error:
E/FirebaseAuth(21546): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17028 A safety_net_token was passed, but no matching SHA-256 was registered in the Firebase console. Please make sure that this application’s packageName/SHA256 pair is registered in the Firebase Console.
I/flutter (21546): This app is not authorized to use Firebase Authentication. Please verify that the correct package name and SHA-1 are configured in the Firebase Console. [ A safety_net_token was passed, but no matching SHA-256 was registered in the Firebase console. Please make sure that this application’s packageName/SHA256 pair is registered in the Firebase Console. ]
I had already get the SHA1 and SHA256 key from the cmd by using the following steps:
In cmd, visited the path where java jdk is installed(in my case:C:\Program Files\Java\jdk1.8.0_212)
Then pasted the following command and hit enter
keytool -list -v -keystore "C:\Users\Mehul Jain.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android
After that i got the key as shown in Screenshot.
copied both the keys and pasted in the firebase Console (as shown in Screenshot below)
App is working correctly. And when I tried signing through test mode (i.e. entering the mobile no. and otp) and run the app with the test mode details, the app was working 100%.
But if I want to add the mobile number from the app and try to get SMS the error comes on the screen. I had tried various other mobile number but still not worked(mobile number are not entered in test mode).
if are using emulator then safety net fails make sure you using a legitimate with Android Device
it is possible that u using wrong keystore. best method for fnding
debug SHA key is Gradle >> signinreport>>rightclick>>run
I suggest you to use this free library OTP_VERIFICATION API
I have also tried this, and it is the simplest API ever.
I've built the App on android studio. When I connect my phone to my PC and build it directly through Android Studio it works. I get the phone verification code and am able to sign in. But when I generate a signed APK to distribute it to others, it always says "Verification Failed" and doesn't let me sign in.
I'm pretty sure there's no problem with the code, because it works perfectly when I build it through Android Studio directly onto my phone.
What Ive Tried:-
I followed the steps in this link and changed the SHA-1 code in my firebase console to the one provided in my Google Console, it still says verification failed.
I also tried to keep only one SHA-1 key in my firebase console which is the one i found in my android project, updated the google-services.json file and tried generating a signed APK, its still says verification failed.
Generate a new SHA1 fingerprint from the console in Android Studio using
keytool -list -v -keystore <absolute path of Keys generated during signed APK generation> -alias <app alias name>
Paste the generated fingerprint in the firebase console and delete the older one.
Hope this works!
I am using NativeScript (Vue app) with the Firebase plugin to allow Google account logins.
The login button redirects to Google sign-in page but I cannot sign in. The error displayed is "This account already exists on your phone."
According to the plugin page this will happen if the SHA1 fingerprints have not been uploaded to the Firebase console.
There is no difference between a physical device or the emulator, neither between "tns run" and "tns build" and then uploading the APK manually.
The command I use is
tns run android --key-store-path ./keyStore.jks --key-store-password <my_keystore_password> --key-store-alias <my_alias> --key-store-alias-password <my_alias_password> --bundle
I followed these steps:
Used keytool to get the SHA1 and added it to the Firebase
console.
Downloaded the google-services.json file and added
it to the app/App_Resources/Android folder.
Used apksigner to
verify the SHA1 and it matches what I have in the Firebase console
as well as the keystore.
When I check the Firebase Analytics page I can see the connection, so I am using the correct app URI etc.
The following is printed in the terminal window:
JS: 'Make sure you\'ve uploaded your SHA1 fingerprint(s) to the Firebase console. Status: Status{statusCode=unknown status code: 12502, resolution=null}'
JS: 'Has the SHA1 fingerprint been uploaded? Sign-in status: Status{statusCode=unknown status code: 12502, resolution=null}'
I noticed another question regarding this on SO but it's not been answered and is a few years old.
Any suggestions/help would be greatly appreciated.
Something that worked for me was to delete the "Platforms" directory from the project files and then run tns build android --bundle.
I would also just verify that your SHA1 fingerprint that you can find with:
keytool -exportcert -list -v \
-alias androiddebugkey -keystore ~/.android/debug.keystore
is the same as one listed in your Firebase settings. (https://developers.google.com/android/guides/client-auth)
The other thing to check would be that you downloaded the google-services.json file after you added the SHA1 fingerprint. But it seems like you've already done most of that.
You have to provide yet another SHA-1 fingerprint.
Locate your debug.keystore (usually in %USERPROFILE%.android\debug.keystore).
Use keytool to retrieve key information as you did with your upload keystore.
Put retrieved SHA-1 into firebase authentication console.
That's all folks.
In release mode, my google sign-in is not working, but it works fine in debug mode. I got a similar question from SO here, but I didn't get perfect solutions.
My handleSignInResult is coming false - How can this be fixed?
Yesterday same problem occurred to me.
Google has released a new signing service in playstore publish console in which google will signin your app with his keystore. After signing , it will give you a new SHA which you have to add in your firebase account.
When you upload app on play store
After signing , it will give you a new SHA which you have to add in your firebase account.
Its Working HAPPY Coding Cheers
Add new SHA1 in https://console.firebase.google.com
Create Release SHA1 using Command Line
keytool -list -v -keystore "E:\Jsk_file\healthNickel" -alias healthNickel
keytool -list -v -keystore "E:\Jsk_file\YOUR_JKS_FILE_NAME" -alias YOUR_JKS_ALIAS_NAME
Enter keystore Password :- YOUR_KEYSTORE_PASSWORD
I had same problem, i did read some posts and was able to get work done by following below steps
Step 1) Please go to https://console.developers.google.com/apis/credentials?
Step 2) Click on create credentials ->select OAuth client ID ->select application type as Android
Step 3) then generate Signing-certificate fingerprint by writing below command in command prompt before that you should have keystore and its path
keytool -exportcert -keystore "D:\PlayStore_keystore\myproject.jks" -list -v
Step 4) after click on enter you will be asked for
Enter keystore password :
Enter password which you have used for creating keystore
Step 5) then it will give details regarding keystore like SHA1,SHA256,MD5 etc.
Step 6) Enter SHA1 as fingerprint and give packagename which is in manifest file
step 7) Click create you will get new OAuth client ID
step 8) now you have got client id you will need to get google-services.json file.
step 9) please goto https://console.firebase.google.com
step 10) if you already have project with that packagename ->go to overview ->click on menu icon where packagne name is written
step 11) select settings goto-> project Settings-> add Android app (in the bottom) -> there will be option called Add fingerprint
step 12) in step 5 you have got SHA1 paste that in certificate fingerprint and save it
step 13) now download new google-services.json file (as it conatins new client id ,certificate_hash etc)
step 14) paste that google-services.json file in app folder in your android project.
step 15) You are good to go...
Make sure you follow all the steps specified in the Guide
. If need be, create a new OAuth Client, new configuration file (the google-services.json) file and do everything step-by-step.
Also try adding a Web Client giving the same credentials.
And for Android as well as Web client give both the SHA1 for debug as well as the release keystores.
In Android Studio, at extreme left you will see a tab saying "Build Variants". Select the release mode there and do everything after that.
Because you are asking about release version of android so I assume you already have signed your application with keystore.
So in order to obtain the SHA1 of your release app.
Go to your /bin in JDK directory.
And run the following command in your cmd.
keytool -list -v -keystore "key store path" -alias "key alias"
This command will give you all the required details of your release version.
Copy the SHA1 string and add it to your firebase console.
You are good to go.
Go to Play store and Search for "App Integrity"
Google play store app integrity
Then
Copy the SHA Keys and Add into the Firebase or Google Cloud signing keys.
and then you are good to go.
Ok I struggled with this and finally I found the solution here it is:
First of all there are three SHA1 keys
Debug SHA1 key
Release SHA1 key
SHA1 key when you google play sign your app
Here you can get debug and release keys and for third key check HarshitG's answer.
There is App signing certificate, this is that key.
Gather those three keys and add them in firebase console under SHA certificate fingerprints
Then Download the google-services.json file and add it in your YOUR_PROJECT_NAME/project/app/ [you'll see it if you change the view to Project from Android]
Rebuild, generate release apk and enjoy :)
Whenever you are using any google api you must add your release hash key on the app you generated in google developer console if you have added hash key for debug.
For a Release (aka, Signed) APK - if you are only deploying to Firebase, you need to add the SHA1 for the same keystore file you used to sign the app.
After successfully adding the SHA1 into the Firebase Project console , get the latest google-services.json and update your project's module local copy.
I didn't see any docs on this so far (seems it's something you have to dig for); found it to be tricky stuff. Lot's of answers on SO. Found the Firebase deployment solt. thanks to:
Answer in this thread to update SHA1 on Google Play, it gave me the idea maybe I need to fix something with SHA1: https://stackoverflow.com/a/44307293/2162226
How to get the SHA1 for a signed APK: https://stackoverflow.com/a/34933381/2162226
in the terminal go to the project folder->android-> paste this command and hit enter ./gradlew signingReport . this will generate set of keys for you .
Then copy the SHA1 and SHA256 keys under release release label.
add them in to your Firebase settings keys section.
Download the googleServices.json and replace your existing googleServices.json with the new one and build the apk again.
hope this helped.
Best And fastest way to fix login social media by flutter application using firebase after upload the app in google play to solve problem
go to google play console than setup > app integrity > from App signing key certificate copy sha1& sha256 and past in firebase account in android app add new sha1 and sha256 .
for facebook error login also copy sha1 from App signing key certificate in google play console go to this website : http://tomeko.net/online_tools/hex_to_base64.php
past in hex string and click covert than copy output base 64 and past inside app setting in facebook development
that's all
If you have two or more firebase projects or the google cloud project, there may be a duplicate SHA1. If such conditions have been explained in this link.
https://support.google.com/firebase/answer/6401008?authuser=0
CAUTION
If exist you put more than one identifier for the same 'signingReport' (copy SHA1 and SHA256 from the same report object) this isn't work, keep this im mind.
This works for me:
Remove all SHA1 in firebase
Run ./gradlew signingReport in android folder and get SHA1 from debug mode.
Run this commmand with your data:
keytool -list -v -keystore your_absolute_path_to_keystore -alias your_alias_from_keystore
(After that you will be promped to digit the password of key and it
wil generate your SHA1 + SHA256 and other infos.)
Copy only SHA1 and paste it in firebase.
Download google-services.json again and move it to your android/app
Before mindlessly running commands n stuff lets get some concepts straight!!
Your app needs to get signed by a signing certificate / keystore (that .jks file) to create a release build. Release builds are created in either Debug mode or Release mode (We'll learn about this futher on)
There are 3 types of these keystore files that you will come across:-
Debug keystore generated by using ./gradlew signingReport
Upload keystore generated by following these instructions
Deployment keystore/Play Signing keystore which is automatically generated by Play Console when you first try to upload a app bundle there. (You can find it at Setup > App integrity > App signing). This keystore stays with Google. You do not have access to its .jks file. So its safe and wont get lost.
Now, I would say, if you wish to get your app on Play Store, DO NOT generate Debug keystore. Generate and ALWAYS use your Upload keystore only.
Why is this important?
Debug keystore are just able to sign your apps in Debug mode (not Release mode).
Even if you try to use flutter build appbundle with --release flag, you are gonna get a app-release.aab which is signed in Debug mode! You can never publish an app signed in Debug mode in Play Store.
Upload keystore can sign your app in Release mode which can be published on Play Store.
Therefore, if you intend to publish your app in future, generate upload keystore by following these instructions and make changes to you gradle files accordingly. Do not generate that debug keystore cuz you wont need it.
This explanation should make you understand that why some answers are wrong which recommend to get a Debug keystore
Now the proper answer to the above question.
Certain Google Play services (such as Google Sign-in and App Invites) require you to provide the SHA-1 of your signing certificate
So if you are signing you app with upload keystore, add the SHA-1 fingerprint of your upload keystore in Firebase Console > Settings Icon > Project settings > Add fingerprint
You can get the SHA-1 of Upload keystore using keytool -v -list -keystore /path/to/upload-keystore.jks
Also, you can get the SHA-1 of Upload keystore and Deployment keystore on Play Console at Setup > App integrity > App signing
Which SHA-1 should I add? There are two SHA-1 at Play Console.
You have to add both SHA-1 fingerprints to firebase.
Why?
For publish reviews you always have to submit your app signed with your Upload keystore. Play Console will accept your app update submission signed with that same Upload keystore only (So keep the Upload keystore safe). That's why, to make that Upload keystore signed App work properly you need to add SHA-1 of Upload keystore in Firebase.
After your publish review is Accepted, your app will be signed again using the Deployment keystore by Play Console (automatic), then it will be published on Play Store. So that's why to make that Deployment keystore signed App work properly you need to add SHA-1 of Deployment keystore in Firebase.