Build for multi arch APK/App Bundles - QtC 5.14.1 - Qt 5.15

ekkescorner

Just in my process to move all my projects from 5.13.2 to 5.15 (will blog about)
For some projects (per ex. needed by QtWorldSummit App) I need signed Release builds:

APK 32-bit (armeabi-v7a)
APK 64-bit (arm64-v8a)
App Bundles (32 and 64-bit) for Play Store

and Debug builds:

APK 32-bit to test on old devices
APK 64-bit

Building APKs I can see if it's signed or not from the name, am I right that the .aab always only is named android-build-release.aab ?

To build a single APK I uncheck 'Build App Bundle' and check only one of the ABIs.
To build the Bundles I check 'Build App Bundle' and check from ABIs: armeabi-v7a, arm64-v8a.

This generates 'android-build-release.aab' and also ONE APK. Which arch is inside the APK - release folder besides the bundles ?
Would be great to get both APKs at once together with the App Bundles. (will open Bugreport)

To get all release builds done. at the moment I'm doing 3 release builds:

bundles
armeabi-v7a - APK
arm64-v8a - APK

Is my way to build all these variants correct or is there an easier way ?

ekkescorner

Building APKs I can see if it's signed or not from the name, am I right that the .aab always only is named 'android-build-release.aab' ?

finally found out, that the .aab from QtC is always unsigned.

added a custom process step to run jarsigner and .aab now is signed

will create a feture request to get this done by QtC similar to APK- signing.

To build the Bundles I check 'Build App Bundle' and check from ABIs: armeabi-v7a, arm64-v8a.

This generates 'android-build-release.aab' and also ONE APK.

have seen that this APK contains both arch

thx @JeromeGodbout helping me with this - see my blog soon