Android: How to know the alias name of the keystore? - android

I have lost my keystore and did not keep any back up of it. I know this question has been asked before but I do not want to extract the password of the keystore. I know the password. I just want to know the alias name and any other details that I might have put in the keystore. Is that possible?
Also, I had developed the previous apk on Android Studio. Now Im using ADT to generate the signed apk. Will it matter with regards to the apk signature process?
Thanks

Related

Uploading apk built on cordova gave error- 'Your apk signed with different certificate as pervious apk.'

The app wasn't built originally by me, so I don't understand keystore, alias and password. But I was given a key that kind of looks like this. I assumed it was one of the three.
oi39.ElqNBBjc72BiKRprL9r4IpVKvtKxT-IioEpVlpW9FnoeKd8Do3jdoce93_komdho30cn_jd003j......Illsiiwk93si0s-D3g
Is it possible to update the app with this, and how would I approach it?

Is there a way to import debug keystore in Android?

We are using Android Studio and we are developing an app using the default keystore. The application is already being used while in development so all clients already have data in their devices.
We now would like to use an actual keystore. However, creating a new one would mean the clients cannot update the application - they would have to reinstall the application which means that they would lose existing data. Is there a way to go around this? Or can we import the existing keystore for release?
It is stored in ~/.android/debug.keystore.
On Windows, this will be something like C:\Users\Username.android\debug.keystore
However, I would advise not to do this, as the debug keys have an early expiration (at least they did with Eclipse, I haven't been able to find anything about Android Studio). Once this date is reached, there will be no option but to create a new key. It's definitely messy, but it'll be easier to clean up now rather than in a years time when you'll have even more users.
You should use the existing keystore itself. While generating the signed apk, You can provide the path to that keystore, keystore password, key alias and key password. This is the only way with which you can generate an updated version of the existing apk.

Updating an Android app with original keystore but different project

Recently my computer crashed and I was only able to recover the keystore and apk of one of my Android apps (already published). Would it be possible to make an update to this app by creating a new project (the original one was lost) and using the original keystore? If so, how? Otherwise, how would I be able to update the app without the original project?
1.Create new project with same package name
2.Write your code from scratch
3.Update correct version code
4.Generate Release APK with your key store and remember to write its password when asked.
5.You are good to update on play store.
As long as application Id and certificate used to sing release APK matches already released binary, you can publish whatever you want.
BTW: Keystore is container for your keys. So if you just recovered keystore it does not automatically mean you recovered your keys (as you might have forgot key password).

"ERROR: Cannot recover key" When Exporting Signed Android App with Existing Keystore

I have an existing keystore with a password and a few keys with different passwords inside for the different apps I have exported and uploaded to Google Play.
Now I have recently imported one of the app's projects, did some significant modifications to it and I am trying to export it using the same keystore and choosing the same alias/password as I did while initially creating it.
The problem is that after the step where I choose the key alias and enter key password I see "ERROR: Cannot recover key".
I suspect that I might be entering a wrong key password (note that the keystore password is the correct one, so this is not the reason for the issue).
I tried creating a new alias and exporting the app under it, but Google Play won't accept this file unless it's signed with the same certificate.
I really don't know how to proceed in this scenario besides trying to brute force the key password. If you think this is the only path, do you know a good brute force cracking tool for keys in a keystore, for which I already know the password to? The keystore is a .reg file, created with Eclipse's Export wizard.
Pretty sure you just entered the password incorrectly. Happened to me just now, stumbled upon your question, hoping for an answer. Didn't find any, so I tried typing the password again. And then it worked.
I stumbled upon the same problem. But I was sure I entered the password correctly. I even typed it to notepad and copy-pasted it to be sure. After that, I created a password cracker for my keystore key password, and found out that the key was actually the one I had been using all along! Tried once more and it worked. So I guess it was a bug of some kind. Maybe you should try closing and reopening eclipse, or restart the computer.

possible to recreate android keystore

There is no backup of the android keystore used on an app in the play store, but there is a backup of the passwords
is it possible to recreate a valid keystore somehow? perhaps by decrypting an apk
I also don't know the "First name" "Last name" and "Organization" of the keystore
No, you cannot recreate a keystore and there is no way to upload an update that has been signed with a different keystore. I ran into this problem a few years ago and I know other devs who have as well. There is simply no good way to fix it. I learned to keep several copies of my keystore in several different locations incase anything every happened again!

Categories

Resources