Android error : Cannot recover key - android

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.

Related

ANDROID Sign APK: FORGOT key password.

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.

Signing android APK with only password

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

Android Titanium App "invalid OAuth consumer key" Error

I have a problem with my first published Android Titanium App
In connection to the cloud I get this error:
"invalid OAuth consumer key"
The keys are properly septate
thanks

Mr. Andrea, Please recheck all the 6 keys in your TiApp.xml file. This issue occurs when the acs-oauth-key-production is incorrect. I've marked the keys in the first picture. You'll get the original keys from your applications as given in the second picture.
Hope it resolved your issue

The problem was on in the code, but not at the level of the server configuration, but had problems.
I created another service I changed the keys
so it all works

Lost Keystore password [duplicate]

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.

Facebook Android - Key Hashes validation

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 ?

Categories

Resources