My problem is much described in this StackOverflow question:
http://stackoverflow.com/questions/21493951/gradle-assemblerelease-uses-wrong-key-certificate
In our old build script, we use the following command for release signing:
jarsigner -verbose -storetype pkcs12 -keystore C:\opt\keystore\cer.p12
-signedjar %signed% %source% 1
This doesn't have any problem, apk's RSA fingerprint match the keystore's
fingerprint.
In the new build tool, we use this gradle configuration mimic the old
signing script:
dependencies {
classpath 'com.android.tools.build:gradle:0.12.+'
... ...
signingConfigs {
release {
storeFile file C:\\opt\\keystore\\cer.p12
storeType pkcs12
storePassword 12345678
keyAlias 1
keyPassword 12345678
}
}
... ...
buildTypes {
release {
... ...
signingConfig signingConfigs.release
zipAlign true
}
}
It doesn't give any error message at signing stage, but the RSA
fingerprient generated is totally different from the original keystore
fingerprint. I am quite confused where does the new fingerprint come from?
My question is:
1. Does the new build tool support pkcs12 store type?
2. Does the new build tool use system default jarsigner? if not, what
signing tool does android-gradle-plugin used inside.
Appreciate if someone can shed some lights on this.
York
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
