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 ?
Related
I have JKS keystore and I remember the password but not alias.
It's said 'No key found with the alias'.
please help.
If you are using Android Studio, then you can find the key alias like this if you know the password,
Enter your keystore path and password, and tap on the folder icon at key alias section,
You will get the key alias list in new window like this,
You can use existing key, or if you want, you can create new one.
can anyone clarify me that is it possible to recover keystore alias key?
i am in big trouble my app is already on playstore and update is ready,and stuck at this point
Here is link bruteforce
using from last two days,nothing works for me..
You can try and find the password in one of the gradle files if you still have the source code and were using Android Studio to develop the app. Try looking for:
..Project\.gradle\2.4\taskArtifacts\taskArtifacts.bin
Alternatively, you can create new keystore and set new password for it with the keytool command below. You don't need original keystore password for it:
keytool -importkeystore -srckeystore path/to/keystore/with/forgotten/pw \
-destkeystore path/to/my/new.keystore
When prompted, create password for your new.keystore and for source keystore password (which you lost) just hit Enter.
You will get warning about integrity not checked, and you will get your new.keystore identical to original with newly set password.
The reason this works is keystore password is only used to provide integrity of the keystore, it does not encrypt data with it, in contrast to private key password, which actually keeps your private key encrypted.
I want sign an APK with a keystore but I dont remember the key password
I have the keystore file
I have the keystore password
I have the alias name
I DONT have the key password (alias one)
Its possible get the alias password without bruteforce?
Thanks in advance,
Yes - you can restore your 'passwords.txt' from backup and look for the password there.
Seriously, the hypothetical possibility to restore the passowrd without long and expensive bruteforce - will brake the cryptography completely.
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.