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.
Related
I have an app in the playstore created with kodular (similar to appinventor),
I started over with flutter and I like the result
However, when I try to deploy on the playstore, the app is refused with a reason: Your Android App Bundle is signed with the wrong key.
Do I have the upload_cert.der file, and how can I sign the flutter app with that certificate?
(i use android studio)
Your Apps key should match otherwise you will not able to update the apps. You can find the keystore in kodular
Hi I have made a simple app and when I want to test it I connect my phone 1 to computer by USB cable and the app run very good then I share the app to my other phone 2 and other phones from phone 1 and when I try to install it on the other phones it says can't be installed.
Is the issue from phones or from the app I wored if I publish it on Google play
It's doesn't work pls help me.
The error appears because Android Studio signs your apk with the debug.key by default. Documentation is here. When you sign it with the release key as Google Play requires, the problem will go away.
Installing an app on your phone requires that the APK file is signed with a certificate. When you install an app to your phone with Android Studio, it generates a keystore with a certificate and signs your app. This generated keystore is insecure and can only be used for development. Most likely your other phone is not allowing you to install the app signed with this insecure key.
To fix this, you need to generate a certificate to sign your APK with. For instructions how to do this, read the official documentation
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'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.
I have create android application with google maps android api key, i have changed the api in manifest and restricted the api on application with fingerprint and packagename, the application manifest say fingerprint:
19:96:C0:DF:1B:E0:34:2C:2D:1C:08:23:3D:03:CA:13:65:76:B9:57
And i have used this for locking application.
But after application submitting to google play store maps not working and log say another fingerprint:
If istall signed apk before submitting to store i have another fingerprint:
BF:C5:88:AC:C1:79:D6:B1:26:02:8D:3F:BD:E8:C7:75:ED:32:B4:10
So why i have 3 fingerprint with same application? How to restrict this api to my application?
Now days Google play store generate own signed SH1 key, So pls you add google play generated SH1 key at google console api, where you register your app at google console app.