Google Play says your upload was signed in debug mode
You uploaded an APK that was signed in debug mode. You need to sign your APK in release mode.Short answer
Google Play does not accept anything signed with the debug certificate that Android tools create for development. Either you uploaded a debug build, or your release build type has no signing config and falls back to debug. Build the release variant, assign it an upload key in Gradle, and upload the result.
Fix it fast
1Find out which cause you have
Check which build variants have which signing config. If release lists the debug keystore, that is the problem.
./gradlew signingReport2Match what you see, then jump to its fix
- 1
The file you picked sits in a debug folder, for example app-debug.apk or a debug bundleYou uploaded the debug build outputFix - 2
signingReport shows Config: debug for the release variantThe release build type has no signing config of its ownFix - 3
There is no .jks file and no key.properties in the projectNo upload keystore exists yetFix
- 1
What does the error look like?
You uploaded an APK that was signed in debug mode. You need to sign your APK in release mode.
Cause 1 of 3
You uploaded the debug build output
1Check
Android Studio signs debug builds automatically with a generic debug keystore, and that kind of certificate is rejected for publishing. Look at where your uploaded file came from.
find . -path '*build/outputs*' \( -name '*.aab' -o -name '*.apk' \)2Fix
Build the release variant instead, and upload that file.
./gradlew bundleRelease
# Flutter project:
flutter build appbundle3Verify
The new file is under a release folder, for example build/app/outputs/bundle/release for Flutter.
ls -l build/app/outputs/bundle/release/Confirmed by developer.android.com
Cause 2 of 3
The release build type has no signing config of its own
1Check
Newly created Flutter apps ship with the release build type using the debug signing config so that flutter run --release works. Until you add your own release config, a release bundle is still debug-signed.
grep -n "signingConfig" android/app/build.gradle.kts2Fix
Create a release signing config from your upload keystore and make the release build type use it. Remove the line that points release at debug.
signingConfigs {
create("release") {
keyAlias = keystoreProperties.getProperty("keyAlias")
keyPassword = keystoreProperties.getProperty("keyPassword")
storeFile = keystoreProperties.getProperty("storeFile")?.let { file(it) }
storePassword = keystoreProperties.getProperty("storePassword")
}
}
buildTypes {
release {
signingConfig = signingConfigs.getByName("release")
}
}3Verify
Run the report again; the release variant should now show your upload keystore.
./gradlew signingReportConfirmed by docs.flutter.dev
Cause 3 of 3
No upload keystore exists yet
1Check
Debug keys are created automatically; release keys are not. If you never made an upload key, there is nothing for the release config to use.
ls ~/upload-keystore.jks android/key.properties2Fix
Generate an upload keystore, then reference it from key.properties and keep both files out of public source control.
keytool -genkey -v -keystore ~/upload-keystore.jks -keyalg RSA \
-storetype JKS -keysize 2048 -validity 10000 -alias upload3Verify
Build again and confirm the release variant uses the new keystore.
./gradlew signingReportConfirmed by docs.flutter.dev
How do I stop it coming back?
- Add the release signing config the day the project is created, before anyone builds an upload.
- Always upload from a release build folder and never from a debug folder.
- Run signingReport in CI before the upload step and fail the job if release shows the debug keystore.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
Related fixes
Mobile apps
Google Play rejects the upload because the bundle is signed with the wrong key
Your Android App Bundle is signed with the wrong key. Ensure that your app bundle is signed with the correct signing key and try again.
With Play App Signing, Play Console expects every upload to be signed with your upload key, not the key Google uses to sign installs.
3 causes, each with a fixMobile apps
Google Play says the app does not support 16 KB memory pages
check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a
Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.
5 causes, each with a fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fix