My backup harddrive is completely broken, and my working pc is after format since that time. I've checked drive by some recovery software, but i can't find any .keystore files on list. Is there any other way to recover keystore? I need this to update my app...
If you lost your keystore file,there is no way that you can update your app in google play and it will cause a signature error.
The only way is create an app with a new package name and upload it to play.
https://developer.android.com/tools/publishing/app-signing.html
Warning: Keep your keystore and private key in a safe and secure
place, and ensure that you have secure backups of them. If you publish
an app to Google Play and then lose the key with which you signed your
app, you will not be able to publish any updates to your app, since
you must always sign all versions of your app with the same key.
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'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 an application in Play Store. I had to change my PC and I configured everything again in new PC.
Now I generated a new APK and my SHA1 key is changed. Now when uploading a new apk to the play store it gives an error saying Certificate is different from the previous APK.
What should I do?
You cannot push an update to an existing app in Google Play without signing the app with the certificate (SHA1) that was used for the first release.
Now your option is either to find the old signing certificate or you have to release your app as a new app in the play store listing (with a new package name).
Before uploading the updated application, be sure that you have incremented the android:versionCode and android:versionName attributes in the element of the manifest file. Also, the package name must be the same and the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update.
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.
I'm currently developing an application which consists on an Android client for SCEP protocol. This protocol provides an automatic method of certificate enrollment and renewal for mobile devices into a PKI.
Due to that, I'm facing with the problem that with the Android version I'm using (4.2) I'm not able to remove user certificates to execute renewal process.
I don't mind if it can be done silently or not, I just want to know if user-certificates removal from Android KeyStore can be done programatically on a non-rooted Android device.
Thanks in advance.