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
Related
I just created my first game using Buildbox and I am trying to upload it to the Google Play Store. Apparently, I have to use Android Studio to turn the game file into an APK. So far, I know how to open it and select "Generate signed APK" or something along those lines, but then I am given a screen like this.
I have virtually no prior knowledge of any of this, so am I supposed to create a new key store path? Do I already have one? How do I do it?
Any tips are appreciated :)
Key Store Path is the location where your keystore should be created.
If you are creating an apk for first time to release in play store, you have to select 'Create New...' ketstore path, where in which you will be promoted to a new window where you can fill in the details:
KeyStore path : select a path in your system (Create a path in any drive eg: *F:\AndroidKeys*)give a name to your key(eg:game).save in here with the specific name for your project (F:\AndroidKeys\game.jks).
Password**: Give some new password and confirm it(Don't forget).
Alias : Enter an identifying name for your key.
Password : Create and confirm a secure password for your key. This should be different from the password you chose for your keystore.
Validity: select time period for validity of key.
Certificate: Enter some information about yourself or organization (like name,..).
Done with new key generation.
Now on the screen you mentioned select the path, key store password,key alias,key password(will be auto filled at first key generation).
click next -- select build variants(debug or release) release in your case, select the signature versions-- finish .
You can find your release apk in app\release folder of your project.
Note: Please do remember the key and the password it should be same for the future update release of your application.
Refer official android developer site for any referece: https://developer.android.com/studio/publish/app-signing
If it is your first time, create new path for example in your desktop. Then choose an arbitrary password and alias for yourself. Write somewhere your settings not to forget them.
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
I have created key hashes as described here (in the end of step 4):-
They tell password is android
It is correct for debug.keystore but I have distr.keystore with different password
Both passwords worked and produced different key hashes when I used them with distr.keystore.
I expected to see: - you have entered wrong password
I think non android password is correct one. But how do I test Key Hash that it is correct Key Hash and another isn't.
u said the both passwords worked with different key hashes , try to use both of them in the facebook side and enter each key hash and try to use your application . it should work if the key hash is right , and the program shouldn't work if the key hash is wrong. but why do u use another file rather than the debug.keystore ?
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 have a problem when i want to run my android application, this is the error message :
Error generating final archive: java.security.UnrecoverableKeyException: Cannot recover key
how to solve this problem?
thankyou
Keystore password and key password both need to be the same. You must be getting this error if they are not same.
Either you have enter your keystore password or Alias password is wrong, that is why you got Cannot recover key Exception.enter correct password for both keystore and alias.
Sometimes if the key is invalid due to expiration,etc then this also happened
I had the same problem, and the solution was as follows:
1- When I changed the key store password,the returns was "error in the password who has tempered the key", in that case the keystore pass is incorrect.
2-If you have the following error, "cannot recover key", in that case the storepass is correct but the password for that alias is incorrect, i remembered my pass and changing, the problem is gone.
you have problem with your key.
This will give you how to info on keys
http://developer.android.com/tools/publishing/app-signing.html#debugmode
To change key in debug mode
(To do so in Eclipse/ADT, go to Windows > Preferences > Android > Build.)
This is one nightmare faced and documentation seem rather not clear on figuring your way out... I had the same issue but I understood after brainstorming.
Now in simplest term...
When you opt in for app signing, Google makes you create a key you use to sign in your app. This is like your legacy key (App signing certificate) and is the bedrock.
Now in uploading, another key is mapped to you which is a second layer ID to you, this lets you update your app.
Now whenever you loose the alias/password you contact google via your mail and they will tell you to create a new keystore that they will reset the old one(upload key) with because they have they legacy key already. Thus at any point in app lifecycle, you don't need to have your legacy key because they have housed it for you already.