AABprovides a new format (
.aabfiles) that include all your app’s compiled code and resources, and defers APK generation and signing to Google Play.
Applivery support for AAB
Although Google Play uses app bundle to generate and serve optimized APKs for each device configuration, so only the code and resources that are needed for a specific device are downloaded to run your app, Applivery is not able yet to provide that feature since we do not have a faithful way to detect the hardware information of the device – mandatory to generate an optimized APK file – since Applivery users normally use their Browsers (Safari, Chrome, Firefox, etc) to download Apps from the Applivery App Stores.
Instead, Applivery takes advantage of the Android App Bundle features to generate Universal APKs that include all the information needed to install your Android applications on any device in the world supported by your App, independently of the hardware. It means that some AAB features can not be fully supported by Applivery such as “Dynamic Delivery” that enable smaller app sizes and feature based delivery.
Applivery uses Android’s Official bundletool to extract the Universal APK from your app bundle. Below we will explain the different requirements to start uploading your app bundles to Applivery.
In the meantime, our team is actively working on providing full support for all Android App Bundle features in a near future in two ways:
- Device prediction to enable Dynamic Delivery from Applivery App Stores.
- Get device hardware information at the Applivery SDK level to enable Dynamic Delivery on updates.
Additional information regarding this could be found in our public roadmap on GitHub.
Configuring Android App Bundle
Step 1 - Adding your Keystore configuration
Go to the Settings > Android App Bundle section of the App where you want to enable AAB. You will need to collect the following mandatory information:
- Keystore: deployment keystore (
.jksfile) used to sign the
- Keystore password: keystore’s password. It could be specified in plain text or
- Keystore alias: specifies the alias of the signing key you want to use.
- Key: specifies the password for the signing key. It could be specified in plain text or
Step 2 - Upload your .aab file as you normally do with APKs
Use one of the following options to upload your app bundle file to Applivery:
- Form the Dashboard, by going to the Builds section and selecting (or dragging and dropping) your
- From the Upload API, using the same method to upload standard
- By using any of the existing integrations with the most common CD & CI platforms.