DeployGate supports both APK files and AAB files (Android App Bundle) as Android app upload options.

How It Works

When an AAB is uploaded, DeployGates generates a universal APK, signs the configured app with a signing key, and distributes the APK to a device. Please note that this process differs from the Dynamic Delivery distribution that takes place when an AAB is uploaded to the Play Store and generates an APK optimized for each device. As of 2019 and the publication of this article, features specific to Google Play, such as On-demand Delivery of Dynamic Feature Modules, are not available outside of the Play Store.

Preparations

AAB file uploads are disabled by default. To enable AAB file uploads, upload or generate an app signing key for the applicable app.

Generate or Upload App Signing Key

DeployGate uses a stored app signing key to generate a universal APK from an uploaded AAB. App signing keys can be created or updated from the signing key management page of the app details screen.

Known Limitations

App Must Be Uploaded in Advance

In order to set up the app signing key, it is necessary to upload the app to DeployGate in advance. As such, the initial upload to DeployGate requires an APK file. An AAB file cannot be used when uploading an app for the first time.

App Bundle Specific Features (such as Dynamic Delivery) Will Not Function

DeployGate uses google/bundletool to generate universal APKs. As such, APKs distributed to devices are not optimized for each device and do not support Custom Delivery options like On-demand Delivery and Conditional Delivery. Additionally, it is necessary to adjust Dynamic Feature Module manifest to the following setting: "dist:include=true"

If you require the App Bundle’s features, please use the Play Store’s Internal App Sharing function.

Distribution of Device Optimized APKs

This feature is not currently supported.

Did this answer your question?