Hello, I am trying to upload an apk, when I do that, I get an error saying that only AAPK signed with V1 jar are accepted, I am using android studio Bumble bee with sdk version 30, I have on my grade to use v1 Signing, but the apk is still signed using v2. Has anybody encounter this problem?
v1SigningEnabled true v2SigningEnabled false
This happens with newer Android Studio versions. If you want you can rollback to previous versions.
For me,
I create an apk in android studio and use the command line to sign.
I made a gradle script to output the command to do the signing
task clover_sign(){
/*
*********************************************
* IMPORTANT
* you must open the archive and the name of 2 files to upoad to clover
* /META-INF/CLOVER_G.RSA
* /META-INF/CLOVER_G.SF
*
* must be changed to
* /META-INF/CERT.RSA
* /META-INF/CERT.SF
*
* using Total Commander is pretty handy for this - can change name inside archive without opening it up and repackaging it
*********************************************
*/
String android_home = System.getenv("android_home")
String android_version = "33.0.0"
String command = "%android_home%\\build-tools\\33.0.0\\apksigner.bat sign " +
" --in \"{your app default dir}\\app\\build\\outputs\\apk\\debug\\app-debug.apk\" " +
" --out \"{your app default dir}\\app\\build\\outputs\\apk\\debug\\app-debug-signed.apk\" " +
" --ks \"{your app default dir}\\app\\keys\\{your keystore}\" " +
" --ks-key-alias {your key alias} " +
" --ks-pass pass:{your ks password} " +
" --key-pass pass:{your key password} " +
" --v1-signing-enabled true " +
" --v2-signing-enabled false " +
" --v3-signing-enabled false " +
" --v4-signing-enabled false "
print command
}
file in all {your **** } with your values.
It is kind of a pain but it works.
I hope someone responds with a better approach.
4 People are following this question.
