Targeting Android 11 required Signature V2 Signing.

[rupeshkumar22]

Currently, the packages are being exported with Signature V1 signing. According to the official android documentation here -

Apps that target Android 11 (API level 30) that are currently only signed using APK Signature Scheme v1 must now also be signed using APK Signature Scheme v2 or higher. Users can't install or update apps that are only signed with APK Signature Scheme v1 on devices that run Android 11.

There is a need to provide the functionality to export the packages with V2 Signing, But first, need to make sure that it won't create compatibility issues.

Testings are required to verify the exported packages on Android 11 devices or emulators with build target version 11.

Below is one of the methods to check the Signature Version of the packages:

[farhazulMullick]

After a successfull gradle sync why I cannot this application like simple android application on mobile
why I cannot run this appliction like other application on emulator

[rupeshkumar22]

@farhazulMullick Hi, According to what I understand from your comment, Are you trying to build and install 'processing-android' project on an emulator through the Android Studio? If yes then this is not a native android app project which you can run on an emulator. The project builds the Processing Android Mode and related libraries i.e Processing Core, AR, and VR. For more information on building the project, you can refer to this page.
Also, For such queries, I would recommend you to use the official community website of Processing Foundation https://discourse.processing.org/
Thanks

[rupeshkumar22]

References for V2 Signing

Google Source Code for V2 Signing
More About V2 Scheme
APKSigner from SDK.

[codeanticode]

I'd see this is critical because apps built with Processing won't be compatible with Android 11 devices unless V2 signing is supported.

[codeanticode]

@rupesh-kumar-lpu So I incorporated the source code in the Android project for V2 signing:

e89b0ab

The exported signed bundle option now generates the V1 and V2 signed packages without error, however, when I try uploading the V2 signed aab to google play, I get the error "You uploaded a file that is not a well-formed zip archive" even though the aab file seems to be a valid zip file when I unpack it on my computer. So i must be doing something wrong.

Mentioning this just in case you can take a look. Thank you!

[rupeshkumar22]

Hi Andres, it's strange to get that play console error despite the code for the v2 scheme seems alright.
Are we aligning the bundle after signing? Not sure if we really need to align bundle.
I'll try signing unsigned bundle manually with apksigner and will compare the packages.
Last time I generated universal apk from bundle generated from project and that worked fine on devices. I am looking into it and will inform at the earliest.
After resolving this one, major implementation to work on would be to automate publishing of packages on central repository.
Thanks @codeanticode