You cannot install an .aab file directly on an Android phone. An Android App Bundle is a publishing format. For local testing, convert it into an .apks archive or device-specific APK splits with bundletool, sign the output correctly, then install the generated APK set on the target device.
Quick Answer
If adb install app-release.aab fails, nothing is wrong with ADB. Android devices install APK files, not raw AAB files. The usual local workflow is: build the AAB, run bundletool build-apks, then run bundletool install-apks against a connected device. For multiple devices, generate a broadly compatible Universal APK or run a separate device-specific split workflow for each target.
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
Why AAB Files Cannot Be Installed Directly
An AAB contains code, resources, native libraries, density assets, language splits, and module metadata. Google Play or bundletool uses that information to generate the APKs that match a device. That is why the file is useful for publishing but not directly installable by the Android package manager.
Manual Steps
- Build a release or staging
.aabfrom Android Studio, Gradle, or CI. - Choose the signing key that matches the install scenario.
- Run
bundletool build-apksto generate an.apksarchive. - Connect the target device and check
adb devices. - Run
bundletool install-apksfor that device. - Launch the app and test login, networking, billing, deep links, push, analytics, and startup paths.
Common Mistakes
- Using debug signing for a release-like test. This can hide signing and store-upload issues.
- Installing APKS built for another device. Device-specific splits must match ABI, density, SDK, and language configuration.
- Using one device-specific split set for many devices. Split APKs generated for one target can fail on another target; use Universal APK mode for broad batch installs.
- Forgetting versionCode rules. Android blocks downgrades unless the app is uninstalled or debug-only flags are used.
- Testing only the universal APK. Universal APKs are convenient but do not always represent Play-style split delivery.
How ADB Pro Helps
AAB Tools is the free focused plugin for converting AAB files to APKS and installing them from a JetBrains IDE. It supports targeted single-device installs for split APKS testing and selected multi-device batch installs with Universal APK mode. In the full ADB Pro workflow, AAB Tools works together with Signing Tools, Device Manager, Bundle Inspector, and Release Readiness so the local install test is connected to the same checks used before publishing.
FAQ
Can I convert AAB to APK?
Yes, but the safer term is converting AAB to APKS or APK splits. A universal APK is possible for some tests, but device-specific APKS is closer to real distribution.
Do I need bundletool?
Yes. Bundletool is the official tool for generating APK sets from Android App Bundles.
Why does install-apks fail with multiple devices?
When more than one device is connected, pass a specific --device-id so bundletool installs the correct split set. If you want to install the same candidate to several different devices, Universal APK mode is usually safer than reusing split APKs generated for only one device.