So I have a client that has sent me a keystore file and told me that is how I will get the APK. I followed the directions for generating an APK from a keystore here:
https://developer.android.com/studio/publish/app-signing#sign_release
What am I missing here? Why am I still loading the default blank project I am trying to load? Have I overwritten something?
i think you miss understood the concept of a keystore .
the keystore is used along with a password to sign an apk or aab of an existing project.
so if a client sent you a keystore how do you expect to get an apk from the keystore file ? it doesn't contain an apk in it .
Related
I have a .apk file. And I want to get the platform key (with .jks or .keystore format)from this .apk to sign another .apk. Is it possible? If yes, how to do it?
If you mean to sign APK by retrieving all data necessary for signing from another APK ... answer is NO.. you need to get that keystone to sign same or another APK.
I am creating an in-app purchase app. I have uploaded apk file once while creating the application in Google Play developer console. But now when I am trying to upload another version of apk file it is showing error of different SHA-1 keys. I have changed the version code and package name is also same. I referred questions here and I got to know that apk should be signed with same certificate.
But my problem is when I export the project from Eclipse to generate signed apk it is not allowing to use existing keystore; moreover when I select existing keystore the dropdown list of alias are empty. So each time I have to create new keystore. Also it is showing "Invalid keystore format" on selecting exiting keystore. Please provide me with some solution to how can I generate an APK with same SHA-1 key.
Is this apk file generated from another computer than the first?
Make sure to have the same .keyStore file on your different PC.
I am working for a client on their Android app. I need to create an APK file which will be deployed to the client's server.
The client does not have the original KeyStore file! In Android Studio it says that the KeyStore file is required! What can I do?
if exists a previous version of the app it can´t be updated because need the same Keystore file, Now you need to create another Keystore to sign your app.
Generate a KeyStore
Signing your applications
I uploaded an android application a few months ago and I will need to upload version-3 soon. But I forgot which key-store file I used to sign the previous APK.
Therefore, how do I check which key-store file I used to sign the APK file?
If you have several keystores with you then you can try making apks with them try uploading the APKs.
If it accepts then you are lucky. This is the original keystone you used while signing the first time.
If you don't have the original keystore then it is not possible as per my knowledge.
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.