Menu
So today I finally update my SDK to 22.0.0 however this creates an error in the AndroidManifest.xml for android:debuggable="false" which means I can no longer externally sign and zipalign my own apks.
I have been signing using my own key.pk8 and certificate.pem, however eclipse ADT requires a keystore.
Does anyone know a way to either build a keystore using my already generated key or find some way around this?
211
You can export the certificate of your new app signature from . jks file in two way: Via CMD/PowerShell or Terminal : keytool -export -rfc -alias upload -file upload_certificate. pem -keystore keystore.
In the menu bar, click Build > Generate Signed Bundle/APK. In the Generate Signed Bundle or APK dialog, select Android App Bundle or APK and click Next. Below the field for Key store path, click Create new. On the New Key Store window, provide the following information for your keystore and key, as shown in figure 2.
So yes, you can use the same keystore to sign multiple apks, without a problem. You can also use the same alias (each alias is a certificate) to sign multiple apks, and it will work. It has security implications, however.
Ok, So I eventually managed to solve the problem.
I downloaded openssl for windows from here
Keytool can be found at E:\Program Files\Java\jdk1.7.0_17\bin
Then using keytool and openssl managed to build the key.pk8 and certificate.pem into a keystore entry
openssl pkcs8 -inform DER -nocrypt -in key.pk8 -out key.pem
openssl pkcs12 -export -in certificate.pem -inkey key.pem -out platform.p12 -password pass:android -name mykey
keytool -importkeystore -deststorepass password -destkeystore .keystore -srckeystore platform.p12 -srcstoretype PKCS12 -srcstorepass android
keytool -list -v -keystore .keystore
The last step is just to verify that the key has been added to the keystore.
100
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With