Install Split APKs Without Missing a Required Split

Confirm that the files belong together

For every APK, verify the application ID, version code and signing identity. Check which file is the base and which files provide ABI, density, language or feature content. Keep the source of the set in your test record.

A set extracted from one phone may be tailored to that phone. It may omit an ABI required by another device, and it may not include on-demand modules that were never installed. Bundle delivery model.

Prefer bundletool when you have the AAB

Generate the package set for the intended test device from the original bundle, then use bundletool's install command:

java -jar bundletool.jar install-apks --apks=app-device.apks

This example assumes that app-device.apks is an already generated, compatible archive. Select the intended connected device using the documented options when more than one is available. bundletool installation.

Use ADB for an explicit authorized set

When you already have the correct individual APKs, ADB supports a multiple-package-file install operation:

adb install-multiple base.apk split_config.arm64_v8a.apk split_config.en.apk

The filenames are illustrative. Include the actual required files for the app and device; this is not a universal three-file recipe. Read the package manager's error rather than assuming any failure is a permissions problem. ADB.

Interpret common failures

Uninstalling can destroy local app data. Do not use it as the first troubleshooting step on a device containing valuable user information.

Verify more than installation

Launch the app, switch relevant language or display configurations and exercise features that depend on native code or optional modules. An app can install successfully while a particular screen fails when it loads a missing resource.

APKLint can help inspect the individual artifacts. Its report for one APK should not be interpreted as validation that the complete split set is installable or functionally equivalent on every device.