My issue is that I have published an APK from my machine, and after that I have formated the machine. Now, I'm trying to create the sign APK from the same machine after formatting, but I am unable to do do.
I am using same keystore .jks file also I provide same .jks file and same alias name & password. I have also tried to do the same from other machines, but not able to do so.
Related
I've been learning programming on Android Studio and already have an app about to publish. Some points are missing for trying to learn by myself and my question may sound silly.
3-4 months ago I generated my first signed apk. Since then as I developed my app, sometimes I generated apks to test my app. When I was generating signed apks keystore file (jks) path
was remembered and I quickly click forward button to generate signed apk. The location of my jks file was "C:\Users\Me\AndroidStudioProjects\MyApp\feature\build\outputs". After Android Studio update I can not generate signed apk with this key. Whatever I do, they all end with "No key with alias '....' found in keystore C:\Users\Me\Desktop\"
Keystore path is always seems as desktop. I can not change it. When generating apk I already select my existing keystore path but Android Studio always looks for keystore file on desktop.
Another problem is alias name mentioned in the error message is different my existing alias name. Android Studio looks wrong place and wrong alias name. So why is Android Studio acting like this? How can I generate a signed apk again?
I recently uploaded my game on playstore made with unity but I forgot the password to the keystore when I tried to build an update.
After hours of googling I've learned the importance of the keystore file. After a few trial and error attempts I finally figured out the correct password.
However, what if in the future my keystore.debug file gets deleted accidentally? Will it be generated automatically again by unity or do I need to make a backup for this file on the cloud?
If I need to make a backup than do I need to backup only "user/.android/debug.keystore", or are there other files I need to backup as well?
Some exaplanation:
debug.keystore (located on user/.android/debug.keystore) as the name implies, it is only used for debugging. That means, it's only used when you're sitting on your computer with the phone connected via ADB and typing code.
When developers release an app. Another keystore is used, the "release" keystore. That is the one you selected when clicking "Generate signed APK" or set on your gradle file, that you had to create a password for it. That file can be located anywhere on your system, you created it, you should know where it is. That one is very important. That one is the one that will allow you to update the app on the Play Store.
Direct answers:
debug.keystore is disposable and you don't have to worry with it.
the keystore used when exporting the .apk file, that one is VERY VERY important and YES, make backup of it everywhere you can! On an external hard-drive on your house, on a USB-drive and at least 1 cloud backup (e.g. Google Drive). If you loose that file or the password, you won't be able to update your app again.
I hope it helps.
You have to differentiate between debug.keystore & release keystore
debug.keystore Android User Guide
When running or debugging your project from the IDE, Android Studio automatically signs your APK with a debug certificate generated by the Android SDK tools. The first time you run or debug your project in Android Studio, the IDE automatically creates the debug keystore and certificate in $HOME/.android/debug.keystore, and sets the keystore and key passwords.
No need to remember as its generated automatically
release.keystore
Needed to publish on google play console, But take care after you generate it and used to release signed version for push to production when you app become published you can only send updates using this key. it will be permanent for you app package name on Google play. You have to backup key and it's protection password too.
I have the app ready so trying to sign it. I read the dev docs. Am using eclipse and adt so started using export. Am able to export a sample app. While exporting they says to have the key. I have created a new file and proceeded and finally I got the output apk. Once whn I opened the key file, I cant read anything. So I am confused.. Will it be readable?? or like the same? Please tell me about the certificate they are mentioning on signing the app, is this same as the one, the file I have created?? Thanks in advance..
Once whn I opened the key file, I cant read anything. So I am confused.. Will it be readable??
Your keystore file (e.g. mykeystore.keystore) should not be readable in a text editor or other such program.
Please tell me about the certificate they are mentioning on signing the app, is this same as the one, the file I have created??
Once you have finished signing your APK using your keystore (see Signing your Application), the APK will contain a META-INF directory that contains a CERT.RSA file, which is the application's certificate. You don't need to worry about this file at all, and it is automatically generated by keytool when you sign your APK.
Your private key (see Obtain a Private Key) is also referred to as your signing certificate, and is what is stored in the keystore. This is the key that you use to sign your application. After you have generated this key using keytool, you shouldn't need to worry about it anymore.
How to extract the apk file using the jarsigner to get the keystore to update my Android application?
This is not mathematically possible. The complete and entire point behind digital signatures is that they cannot be reverse-engineered except with more computing power than anyone will have.
You should already have the keystore for your app -- you used it once already to sign the APK file. If you lost that keystore file, restore it from a backup.
I have an app that's been developed on two computers. The Keystore was created on one of the computers but I want to use that Keystore to export the signed APK on the other computer. I moved the Keystore file over with a flash drive and selected to use an existing Keystore in Eclipse. After entering the password I got the error below when I had to select the alias. It wouldn't let me select an alias so I couldn't continue with the exporting. Anyone know if Keystores can be created on one computer and used on another, or how to fix this problem?
Nevermind, I found the answer to my own question. Apparently the keystore file I transferred over was corrupt.