I've made a chat app that uses Firebase's feature Real-time database.
I face a problem with google authentication. The problem started when I downloaded the app from the Play Store, the authentication was working perfectly when I was running the app in debug mode. When users try to sign in they get a toast message code:10 message:10.
I would like to note here that: I've added the SHA1 fingerprint. How can I solve this?
*Not sure if this is helpful but I've followed step by step this tutorial
You need three keys in order to make it work:
The debug key. Informations here.
The release key. Informations here.
Google Play App signing key. Informations here.
All these keys are needed in order to make the sign-in process work.
Other informations here.
After generating SHA1 for release key, I forgot downloading the new google-service.json file that caused the same error.
Make sure you follow the instruction https://developers.google.com/android/guides/client-auth to generate and add debug/release SHA1 to firebase console and download google-service.json after updated.
If you use Use app signing by Google Play option, you need an additional step:
After uploading app into google play console, go to Release management > App signing, copy SHA1 and paste to firebase console
Update
In the new google play console, the App signing key can be found as following:
Setup > App signing
Make sure you have added signed SHA1. If you are using debug one then it will not gonna work for live apk.
You need to put "debug.keystore" in this path C:\Users\USER_FOLDER_NAME.android
then in Android studio follow the below steps
1. Run your project
2. Click on Gradle menu
3. Expand Gradle Tasks tree
4. Double click on android -> signingReport
You can see SHA in Run Tab
for more information see link
For me the problem was that i registered app and enabled google signin on Firebase console but I was testing with the debug version of app which has slightly different package name (same name but ended with .debug) so it was not working because the debug app is not yet registered. so additionally to my release app i also added the debug app to the firebase project for the app and it generated it's own google-services.json which i download and set to src/debug/google-services.json.
I believe this might be useful to some one else.
Related
I am trying to login in Android app using Firebase Auth (phone).
It works perfectly when in debug apk.
But it does not work if the apk is signed (using the signature.jks file). and says : "Unknown error" in phone after input of phone number.
I looked through different question in Stack Overflow too but they suggest to add SHA key to playstore console. But that does not make sense. What if I want to publish the apks in amazon market or other android app market? Firebase forbids that?
Is there any solution to it? I must be missing a tiny point but I am lost to find it.
You don't need to add SHA-1 fingerprint of your release key to Google Play Console. But, to enable Firebase Authentication, you need to add it in Firebase Console. Follow the steps given here.
I am coming right now from solving this issue.
Each playstores impose their own SHA1 and SHA256 key. So grab that and go to your firebase console and add it there.
Voila it will work!!
I have a problem with the Google Login.
I've implemented the google-services.json file. The File contains two SHAs, the debug and release SHA. I've inserted both SHA on the firebase settings menu. Downloaded the google-services.json and placed it into the /app folder.
The release SHA has to be the right one because I followed all steps to get the release SHA with the keytool!
When testing my App on the Emulator everything works fine but when uploading to the Google Play Store (Beta Build), I get the Developer Error.
--> I know that the Developer Error means that it must be a Problem with the SHA.
I've already used Google Login in another App and there it works fine and I've done the same steps in my current Application.
Can you guys please help me!
Elias
Make sure your sha is valid. Note that debug and release builds should be signed with different keys, so you actually need to provide 2 sha chekcksums. Also, look here: https://support.google.com/googleplay/android-developer/answer/7384423?hl=en
I hope you are not going to upload to Google Play app signed with debug key (which is wrong)
In Debug mode, Google Play Games shows it's loading screen and I can even log in. However, afterwards I am receiving this error in a clean message box:
The application is incorrectly configured. Check that the package name and signing certificate match the client ID created in Developer Console. Also, if the application is not yet published, check that the account you are trying to sign in with is listed as a tester account. See logs for more information.
In Release mode, the game crashes and I am receiving this error in Android Studio:
Access Not Configured. The API (Google Play Game Services API) is not enabled for your project. Please use the Google Developers Console to update your configuration.
In Google Play Developer Console, all the marks are ticked. I don't understand why it is not working. Should I do something with the SHA key or client ID?
I did not publish my settings yet, but it says The Google Play game services settings are ready to test. I use my developer account as test account on the same device as I am testing on.
I was using the wrong SHA1 keys. I had to create a new GPGS Game and perform step 3C on this page: https://developers.google.com/games/services/console/enabling
I am developing an app that uses google's turn based multiplayer API. I have two devices that I am using to test on. The first phone, which uses the developer gmail, can sign into the multiplayer just fine. The second one, whether I install the app directly from the computer or I install the signed apk with the release keystore, gets this error every time I try to sign in with it:
Failed to sign in. Please check your network connection and try again.
The second phone uses a gmail account that is set as a testing account for the app in the developer console. I am not positive what the issue is here. And yes, I have made sure that there is not an actual network issue as I am able access the internet just fine.
I appreciate any help. Thanks.
After troubleshooting for a while I realized that my issue was that my SHA1 fingerprint for my signed apk and the SHA1 fingerprint for the project that I had setup in my google developer console were different. To fix this I just unlinked the application from my game and relinked it using the correct SHA1 fingerprint.
To create facebook android native app we need to provide our Android application signature in facebook app settings. whenever i export some test application and provide the key and class name on application it is working perfectly , i am wondering how to make that workable on emulator... how to create a keyhash in emulator ... any ideas?
FYI i am following the tutorial below
http://www.androidhive.info/2012/03/android-facebook-connect-tutorial/
The app which is installed on emulator from eclipse is typically signed by default android debug key store, You will generate key hash from using that android key store, add that hash also to the your facebook app setting for android app, So there will be two hashes, one for debug keystore and the second one is generated by the key store which you will use to sign your app to test on real device.