I am using Firebase's Google-Sign In and it works when I use my application in Genymotion but when I create the signed apk to install it on other devices the Google Sign In does not work, it says it is error 10, however my debug key SHA1 is correct in firebase. How can I make my application work on other devices with the Google Sign In?
I am making my app in java - android studio
You also need to add the signed APK SHA1 in the firebase. You can get it by using the following command:
keytool -list -v -keystore <your keystore path> -alias <your alias>
After that, put the new google-services.json file in your app and make a release APK.
You need to download the different google-services.json in the release mode to make it work. Firebase provides different google-services.json for debugging and release mode and we need to make sure we are using the right one when creating the build. Please go to your firebase console and create a release mode JSON file for signed APK.
I am using login with amazon in android. I got all the certificate like(SHA256,MD5 for release mode) and its working fine in release mode but when i publish in Google play store it showing me api key error.
java.lang.IllegalArgumentException: Invalid API Key
Any help is appreciated,thx.
You are using Upload-Cert SHA, You should change your API SHA to Play Store App-Signing SHA.
thanks to # Berat Eyüboğlu now my problem is solved. i just want to add more details. After following all the steps we need to run command(for that java have to install in the system)
keytool -printcert -file your.RSA
after that i got all the certificate that i used for api key.
Steps
go to build Generate Signed Apk (in android studio)
After getting signed apk just rename the APK extension to ZIP if necessary Unzip the APK file and extract CERT.RSA .
run this command in command prompt keytool -printcert -file CERT.RSA. (Keytool is located in the java/jdk/bin in windows) all the certificate like MD5,SHA1,SHA256 display command prompt.Use that details for API key.
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.
I am using Google Maps V1 API key. If i Itaking the apk from bin folder, the Google Maps will shown in application. But if I export the project and deploy the exorted apk the google maps do not show in the application. If anybody knows the reason, kindly share your thoughts. Thank you.
When you develop and run an application locally, you are actually signing it with a debug key.
When you export, you are signing it with a different, production key.
Google Maps requires your api key to match the key you sign your app with. So you will need 2 different api keys depending on whether your apk was made via debug key (copying it from "bin") or production (exporting).
What's happening to you is when you export your app, the key is not matching what Google Maps API thinks it should be, so it's not working.
Read more about signing apps here.
Please follow these steps to get Release SHA1
Find your .jks path which is used while creating signed apk.
Ex: /Users/dharm/Documents/Android/test.jks
Copy your jks file name and put in the end of line number 3
Ex: test.jks
Open your terminal and enter this command keytool -list -v -keystore "keystorepath" -alias "keyalias"
Ex: keytool -list -v -keystore /Users/dharm/Documents/Android/test.jks -alias test
When you will press enter it will ask for Enter keystore password. So please enter your key store password.
If you do all the steps successfully then you will get entire information of this certificate(key store).
Ex:
MD5: D2:52:A1:7C:14:9F:D5:DD:64:35:E2:3F:74:CA:C5:E7
SHA1: D3:32:AA:09:81:71:50:D2:47:20:43:B2:13:A2:D5:55:4B:A7:DC:3C
SHA256:
27:8A:84:C5:C3:CE:98:47:A7:73:E2:87:91:5E:5A:A2:F4:B8:D4:D4:0E
Now you can put this SHA1 key on google console( SHA-1 certificate fingerprint).
Hope it will help you.
For Video Kindly have a look on it
https://www.youtube.com/watch?v=g75cZXjmuj8&feature=youtu.be
I put the key directly in the manifest and began to work.
I've completed a app in phonegap and would like to publish this on the google app store. Every time I download the apk file its in debug mode. How do I go about signing it with a key or keystore to get this to upload into google play as google will not upload it into my account in debug mode.
I'm doing something wrong but can not see how in build.phonegap.com you can sign the app?
Please help
Thanks
Use this command from the terminal or command prompt to generate keystore file:
keytool -genkey -v -keystore myAppKey.keystore -alias myAppKey -keyalg RSA -validity 10000
This will generate myAppKey.keystore file.
That you have to upload at build.phonegap.com site under your application settings.
There you will get signing settings so add your keystore and then select that signing key for your application.
By this phonegap will regenerate android builds and you will get APK which will be used to publish in the google play market.
REFERENCE :
how Google suggests creating an Android keystore
Getting the illegal option too - something about copy/pasting from the post above is causing that. If you delete the '-' characters and type them manually using the '-' on your keyboard then it works :)