This question already has answers here:
I lost my .keystore file?
(12 answers)
Closed 8 years ago.
I have my app's latest APK file and full source, and My app's private key of the keystore.
But I lost my keystore file... so I cannot sign my app and update my app..
Anyone know the answer?
If you lost your keystore then there is no way that you can update the app in play sore( it will cause a signature error )! The only way is that you can create an app with a new package name upload it to store and remove the old app.
Actually there is no way to recover your keystore in other way than with tools for recovering deleted files in your OS.
There isn't any tool for pulling keystore from your device or application. Even Google can't restore your keystore from your Google account.
The thing is different when you only lost your password. See https://code.google.com/p/android-keystore-password-recover/
Sorry dear unfortunately you can not update new version of the same application on android play store. you can upload new application with new package name and keystore file. But Google will not allow you to upload new version with different keystore file.
Hope it will help you.
The keystore doesn't need to be uploaded, it needs to be integrated into the apps .apk.
Make sure your building the app for release, in eclipse go to file -> and export the app. This will build it with your release keystore instead of the debug keystore.
When you first export your app and eclipse makes you a keystore it is saved in the eclipse\ folder on your computer, try looking there for it. See this post for where your keystore file should be on your computer.
Related
I have published my app on Google play a few days​ ago and since then i had to uninstall and reinstall my Android studio. Now I don't have the signing key anymore. Is is possible to make the exact same or i can't update my anymore on Google play?
Signing key is a jks file independent from AS.
If you have lose that file, you can't update your app anymore.
As mentioned in this other answer
You can create a new keystore, but the Android Market wont allow you
to upload the apk as an update - worse still, if you try uploading the
apk as a new app it will not allow it either as it knows there is a
'different' version of the same apk already in the market even if you
delete your previous version from the market
Do your absolute best to find that keystore!!
When you find it, email it to yourself so you have a copy on your
gmail that you can go and get in the case you loose it from your hard
drive!
You have to save the jks file in a directory different from the Android Studio one. It is not related to Android Studio
I suppose if you change pakage name and app name it shouldn't give you any problem on google play console. But you can't update that one, sorry. Try your best to recover the jks file!
This question already has answers here:
Generate signed apk android studio
(12 answers)
Closed 6 years ago.
What is the easiest way to sign an Android apk file, if you don't have an existing keystore?
I read many tutorials on the internet that suggest that it's necessary to create a keystore with a command line tool and that therefore Android Studio can't do the task on it's own. Is that still true?
Otherwise is there an easier way to go about the task?
The existing StackOverflow question on APK signing has many Eclipse-specific answers, so I decided to ask a new question.
You can create a keystore from Android Studio itself.
Just go to Build -> Generate Signed APK -> Select your module. You will be able to select an existing keystore or to create one. To create it, you will need to enter a few informations about yourself, and two passphrases, one for the keystore and one for the alias. Then you will be able to sign your apk. Later, you will have to reuse the same keystore.
Make sure to save the keystore, because only the apps signed with it will be allowed to be uploaded to the Play Store, and to update on devices.
For more informations, as always, Android documentation
This question already has answers here:
I lost my .keystore file?
(12 answers)
Lost my keystore for uploaded app on android market [duplicate]
(2 answers)
Closed 8 years ago.
I'm generating a signed APK from Android studio. However, for some reason I can't seem to use the keystone I used previously. Android studio keeps complaining "Keystore was tampered with or password was incorrect". I believe the password is correct.
Anyways, I created a new keystone and generated my signed APK. However, when I try to upload this APK in Beta Testing by clicking on button Upload new APK to Beta I get an error:
You uploaded an APK that is signed with a different certificate to
your previous APKs. You must use the same certificate. Your existing
APKs are signed with the certificate(s) with fingerprint(s):
Question
How can I upload a new APK to my Beta with a different certificate? Or Is there a way to reset password for my .jks file?
My goal is to simply push a new beta version out.
Quick answer: You can't.
Without the certificate you can't upgrade an app, making it's package also "locked" in the last APK you've uploaded.
Now.. you either manage to find the correct password (assuming you're using a wrong one and that's the problem) or.. you'll have to change the app to a new package name, and warn you're users on the description of the old app or something like that...
Several people had the same problem before:
Lost my keystore for uploaded app on android market
Retrieve Private Key for Existing Android App
...
You can't upload the new APK to beta. You need to use the same keystore file as you did for the original app. My guess is your password is wrong, based on the error message you're getting. I would try some the keystore password crackers out there to see if you've got a close password.
An interim fix would be to change the package name on the application, and upload it as a new one to beta, but you can't make any updates to your existing app if you don't have the correct keystore/password combo.
I have an android app which is available on google play.
While creating an apk for release, there was a keystore that was created for signing.
My question is, if after the release, I have some enhancements underway (like facebook or google+ integration), which requires that the dev registers his app using the keystore, which keystore do I use?
Should it be the debug keystore (~/.android/debug.keystore) or the one that was created while packaging my app?
EDIT
Thanks for the answers so far.
To confirm, from the below answers I understand that, when testing this enhancement (before deploying the app to play store) & to register my app at facebook, I will be using the keystore that was used for signing the first apk file for this app and NOT the 'debug.keystore'. Correct?
But, while testing, wouldn't my app be sending 'debug.keystore', if I am building on eclipse platform? Or does the 'debug.keystore' become invalid once I have a new keystore generated for creating the previous apk file?
It's rather too confusing, and want to be clear with this...
You have to use, keystore which is used for generating apk file for playstore. Dont use another keystore, becoz it will give new one but wont updated the old one.
debug keystore (~/.android/debug.keystore) is not going to work for you.
As you mention that your application is already available in Google Play, that means while singing your application it ask Create new Keystore or use Existing one
Then choose Use existing keystore
Give your existing keystore path, and password.
This will give you a build that you can release in Google Play..
Before that make sure that increase the android:versionCode and android:versionName
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="YOUR_PACKAGE"
android:versionCode="1"
android:versionName="1.0" >
Hope this help you.
Plz ask if having any sort of problem.
You have to use your signing keystore which you used while uploading your app to developer console. The one that was created while packaging your app
only used for your signing keystore because already you release the application in play store so you can use new key that time is not release for updated version it's a one of the new application so you can use previous kestore for your updated appp.
This question already has answers here:
How can I create a keystore?
(12 answers)
Closed 9 years ago.
This is my first android app that I would want to publish in the Google Play Store. I have followed the steps from this article.
However I get stuck at one step for specifying the keystore selection. Using the use existing keystore my path
C:\Users\joyson.android\debug.keystore
I suppose this is the debug.keystore which cannot be used for publishing the app. Can someone please suggest how can I do this? Gone through most of the links however the one above was simple and straightforward. Also I am using Eclipse Tool. Any help would be great.
Follow this tutorial about Build Android application package file (APK) using Eclipse IDE and Android Developer Tools (ADT) Plugin. In here describe how to Create new keystore.
You can go with the "Create New Keystore" option if you are signing that application for the first time. Provide the details as described in the link and you will get signed APK in the end.
File->Export->Android Application
Select Which project to be exported
Then click Next
Create New Keystore and fill it. Specify particular location where your keystore to get generated.
And finally it will ask where to save apk file.Specify the location
It will be your signed apk. Remember your password forever for next updates