To install an Android App Bundle on a device, convert the AAB to an APKS archive with bundletool, sign it with the correct keystore when needed, select the target device, and run an install step that matches the device configuration.
Why AAB Installation Is Different
An AAB is not directly installed like an APK. It is a publishing format that contains modules and resources from which device-specific APKs are generated. For local testing, bundletool creates an APKS archive and installs the split APKs that match a connected device.
Manual Workflow
- Download or locate a compatible
bundletoolJAR. - Build or select the release
.aabfile. - Run
build-apkswith keystore information for signed output. - Select the target device when multiple devices are connected.
- Run
install-apksfor the generated APKS archive. - Launch the app and verify variant-specific behavior.
java -jar bundletool.jar build-apks \
--bundle app-release.aab \
--output app-release.apks \
--ks release.jks \
--ks-key-alias release
java -jar bundletool.jar install-apks \
--apks app-release.apks \
--device-id emulator-5554
Common Mistakes
- Trying to install the AAB directly. Devices install APKs, not raw AAB files.
- Using the wrong bundletool version. Old bundletool versions can fail with newer bundle metadata.
- Forgetting signing details. Release-like testing should use the same signing assumptions as production.
- Installing to the wrong device. Multiple connected devices require explicit device selection.
How ADB Pro Helps
AAB Tools wraps bundletool workflows in the IDE, including AAB-to-APKS conversion, signing, and installation. Signing Tools handles keystore-backed signing and verification, while Device Manager helps select the right connected target.
FAQ
Can Android Studio install AAB files?
Android Studio can work with app bundles in some workflows, but local device installation still relies on generated APK splits.
What is inside an APKS file?
An APKS file is an archive containing split APKs and metadata generated from an app bundle.
Do I need a release keystore for local AAB testing?
For production-like testing, yes. Debug signing can hide issues that only appear with release signing and distribution settings.