Play Console: You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode
The bundle was signed with the debug keystore; Play only accepts release-signed uploads.
signed in debug modeYou need to sign your APK or Android App Bundle in release mode Meaning
Building the release variant without a release signingConfig (or Flutter/RN defaults that reuse debug signing) produces a debug-signed artifact.
Common causes
- release buildType uses signingConfigs.debug
- Uploading the debug build output
- Flutter/React Native template default signing
⚡ Quick fix
- Create an upload keystore and a release signingConfig
- Build bundleRelease and upload app-release.aab
- Use Play App Signing with your upload key
Detailed fix by platform
Gradle
- kotlin
android { signingConfigs { create("release") { storeFile = file("upload.jks"); storePassword = System.getenv("KS_PASS"); keyAlias = "upload"; keyPassword = System.getenv("KEY_PASS") } } buildTypes { release { signingConfig = signingConfigs.getByName("release") } } }
How to diagnose
- Signer — keytool -printcert -jarfile app-release.aab
- Build — Which variant was uploaded?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Android
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026