Google Play Console only accepts .aab files now. This is a very common typo 🙂
Below is a VS Code–friendly way to create an .aab using Gradle (no Android Studio required).
Prerequisites
Make sure you have:
- Android project (with
build.gradlefiles) - JDK 11 or 17 installed
- Android SDK installed
- Gradle Wrapper (
gradlewfile in project root)
If your project already builds APKs, you’re good to go.
Step 1: Open Project in VS Code
- Open VS Code
- Open your Android project root folder
- Open the Terminal in VS Code
(Ctrl + ~orView → Terminal)
Step 2: Create the AAB File
Run this command from the project root:
Windows
gradlew bundleRelease
macOS / Linux
./gradlew bundleRelease
Step 3: Locate the .aab File
After the build finishes successfully, your .aab file will be here:
app/build/outputs/bundle/release/app-release.aab
This is the file you upload to Google Play Console.
Step 4: (Optional) Sign the App Bundle
If your app is not already signed, configure signing in:
app/build.gradle
android {
signingConfigs {
release {
storeFile file("your-keystore.jks")
storePassword "storePassword"
keyAlias "keyAlias"
keyPassword "keyPassword"
}
}
buildTypes {
release {
signingConfig signingConfigs.release
}
}
}
Then rebuild:
gradlew bundleRelease
Google Play also supports Play App Signing, so you usually only need to sign once.
Step 5: Upload to Play Console
- Go to Google Play Console
- Select your app
- Go to Production / Testing
- Upload
app-release.aab
Common Errors & Fixes
❌ SDK location not found
➡️ Set ANDROID_HOME or local.properties
❌ Execution failed for BundleTask
➡️ Run:
gradlew clean
gradlew bundleRelease
Summary
âś” .aab is the correct format
âś” VS Code + Gradle is enough
âś” Command: gradlew bundleRelease
âś” Upload app-release.aab to Play Console
