App Center now (since Dec 17, 2020) signs Android applications using APK signer internally, instead of JAR signer which was used previously. This seems to have already been documented and has "fixed" as of (Dec 17, 2020)Īnd is similar to what referred to as shared by of Android 11, it's mandatory to use the APK signer (if you use API level 30) as it will set some extra schemes "APK Signature Scheme v2 now required". It should be noted that this is a DevOps pipeline. I chose the build tool version 29.0.2 arbitrarily, there are many versions to choose from and you'll need to decide which version is best for your application. "C:/Program Files (x86)/Android/android-sdk/build-tools/29.0.2/zipalign.exe" -p 4 input.apk output.apk JarsignerKeystorePassword: '$(keystorePassword)' After I signed the apk file, I had to run the zipalign tool as an additional task, this is what my yaml looks like. So here's what I did to work around the problem. If you at least give us an approximate ETA then we will be in place to understand how long we will have to rely on had the same problem with my apk not working in appcenter and I couldn't make the new jar files work in a pipeline. I was able to do this from pipeline but the version number doesn't change, it always remains same.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |