I selected 'Build' --> Generate Signed Bundle or APK
I choose Android App Bundle and click next
Here is see my Module which lists my app name
Then there is a Key Store path which is blank?! What do I do here? Do I hit the "Create New..." button to create a new key since its the first time building my app?
The other textsboxes are
Key store password which I would image i provide on the new key store path, if i need to create new key store
then there is Key alias, which I have no clue on and key password.
Why is this sooooo complicated?
Can someone help me understand how I can just create a new android app bundle?
You have to create the key first, when creating the key you'll set the alias and the password, here's the documentation detailing the process:
https://developer.android.com/studio/publish/app-signing#generate-key
I know the step of siging the application.
problem is i lost my builded key for siging and i only know the password that key built with it.
is it possible to make another key with same password and use it for sign porgram to update old one ?
or should i rename my application and make new one ?
There is no way that you can update the app in playStore.You must be create an new app with a new package name and remove the old app, then republish new app
This question already has answers here:
How to handle a lost KeyStore password in Android?
(42 answers)
Closed 4 years ago.
I want to update my Application to playstore and I lost my keystore password.Now I am trying to create a new one . Will there be any problem if I build APK with another keystore password ?
As #CRUSADER said, Android Keystore Password Recovery might work for you. I could retrieve my password with it. Here is how to do that. I was on Windows 7.
Run the following command,
java -jar AndroidKeystoreBrute_v1.05.jar
Then you will get the following guide,
AndroidKeystorePasswordRecoveryTool by M#xiking
Version 1.03
There are 3 Methods to recover the key for your Keystore:
1: simply bruteforce - good luck
2: dictionary attack - your password has to be in the dictionary
3: smart dictionary attack - you specify a dictionary with regular pieces you use in your passwords. Numbers are automat
icly added and first letter will tested uppercase and lowercase
args:
-m <1..3> Method
-k <path> path to your keystore
-d <path> dictionary (for method 2 and 3)
-w saves the certificate in a new Keystore with same passwort than key
-start <String> sets start String of the word (for method 1)
-p use common replacements like '#' for 'a'(for method 3) WARNING - very slow!!
-h prints this helpscreen
Max memory: 247M
I've used method 2 because I had some guess of my password. I typed the following command,
java -jar AndroidKeystoreBrute_v1.05.jar -m 2 -k android.keystore -d dict.txt
In case you might wonder, my dict.txt was something like this,
gussedpassword1
gussedpassword2
gussedpassword3
I could successfully retrieve my password and alias.
Well, you are not the first to lose keystore password..
I use this one for bruteforce when I got stuck: Android Keystore recover
You can go with few guesses.
And as #StinePike mentioned.. you cannot continue updating your existing applications
There will be no problem for uploading new application. But you can not continue updating your existing application with new keystore. You need to create new applications by resubmitting them if you want to update your previous applications.
Always preserve the keystore with a best possible way :(
If you have lost the password to the keystore, then the only option is to create a new signing key. There will be no problem doing so.
However, you will not be able to update the existing application. And neither can you upload another application with the same package name.
For example, if you current package is:
com.example.mycurrentapp
You will need to use a different package name to go along with your new signing key. For example, you can change the package name to:
com.example.mynewapp
The above, are of course, illustrations. ;-)
The Google Play ecosystem identifies different applications using their package names and therefore, they have to be unique. Unfortunately, if you have a good user base, unless they install your new app, they will not be able to get updates to the older app.
It's unfortunate, but when you lose your keystore, or the password to your keystore, your application is orphaned. The only thing you can do is resubmit your app to the market under a new key. You will not be able to update your app without the key.
You will have to publish your app again with a new keystore and under a different package name, or remember your password.
I did not properly create the keys, where he is now?
I created the keys, where I create the application
where keys is now? (there is only one file LM.apk, but he did not keys)
You're are misundersting the keystore :
The keystore is a file which identify you (to securize your release), don't name it *.apk, it's not your application build
You can store as many key in your keystore, one for each application you want to sign with
So you just have to create a first key on your keystore by providing an alias and a password
Then you'll have 1 password for opening your keystore and one for signing with the desired key (alias)
I'm just about to submit an application to the Android Marketplace.
There is this message when I try to upload the app:
Remember to change the public key in updates for this application to match your new public key on the Edit Profile page
Where can I find the public key?
I went to http://market.android.com/publish/Home and click on "edit profile" but I don't see any public key there.
Thanks,
Tee
When using eclipse to do development, right click the project and select Android Tools Then select Export Signed Package (or something similar to that). It will walk you through creating your private key. Make sure you save the key because you will need to use the same key to update the application in the future on the market.