Android apps

APK vs Android App Bundle (.aab)

Why Android App Bundles (.aab) are rejected with error 4001501 and how to build or convert an installable .apk.

Why .aab archives are rejected (Error 4001501)

An Android App Bundle (.aab) is an upstream publishing archive containing uncompiled split resources and BundleConfig.pb metadata intended exclusively for Google Play's server-side signing pipeline. Android phones and tablets cannot install .aab files directly—downloading an .aab onto a device always fails.

BuildDrop inspects both the file extension and internal ZIP entries (BundleConfig.pb) and immediately returns numeric error 4001501 with guidance on generating an installable .apk.

Building a signed .apk in Android Studio or Gradle

In Android Studio, select Build -> Generate Signed Bundle / APK… -> APK, or build from your terminal / CI pipeline:

# Build a debug APK for internal QA:
./gradlew assembleDebug

# Or build a release-signed APK:
./gradlew assembleRelease

Converting an existing .aab into a universal .apk with bundletool

If your release pipeline only archives .aab artifacts, convert any .aab into a single universal .apk using Google's bundletool:

bundletool build-apks \
  --bundle=app-release.aab \
  --output=app-universal.apks \
  --mode=universal \
  --ks=release.keystore \
  --ks-key-alias=upload

unzip -p app-universal.apks universal.apk > app-universal.apk