Play Console warns that the bundle has native code but no debug symbols
This App Bundle contains native code, and you've not uploaded debug symbolsShort answer
Release builds strip native libraries, so Play cannot turn native crash traces into function names. Set ndk.debugSymbolLevel to SYMBOL_TABLE or FULL on the release build type so the bundle carries the symbols, or upload native-debug-symbols.zip by hand.
Fix it fast
1Find out which cause you have
Check whether the release build type already sets a debug symbol level.
grep -n "debugSymbolLevel" android/app/build.gradle*2Match what you see, then jump to its fix
- 1
The warning shows for an .aab and debugSymbolLevel is not setThe release build does not include a symbols fileFix - 2
You use FULL and the symbols file is very largeThe symbols file is over the size limitFix - 3
You upload APK files, or the symbols are not picked up from the buildYou ship an APK, not a bundleFix - 4
Unable to extract native debug metadata from ... because the native debug metadata has already been stripped.A dependency's libraries are already strippedFix
- 1
What does the error look like?
This App Bundle contains native code, and you've not uploaded debug symbols
Cause 1 of 4
The release build does not include a symbols file
1Check
Native libraries are stripped in release builds, which removes names the Play Console would need. AGP can add a symbols file to the bundle itself.
grep -n "ndk" android/app/build.gradle*2Fix
Set the level on the release build type. SYMBOL_TABLE gives function names; FULL adds files and line numbers and makes a larger file.
// android/app/build.gradle.kts
android {
buildTypes {
release {
ndk {
debugSymbolLevel = "SYMBOL_TABLE"
}
}
}
}3Verify
Build the bundle again and upload it; the warning is gone.
flutter build appbundleConfirmed by developer.android.com
Cause 2 of 4
The symbols file is over the size limit
1Check
The native debug symbols file has a limit of 1.6 GB.
ls -lh build/app/outputs/bundle/release/app.aab2Fix
Use SYMBOL_TABLE instead of FULL to make the file smaller.
ndk {
debugSymbolLevel = "SYMBOL_TABLE"
}3Verify
Rebuild and upload the new bundle.
flutter build appbundleConfirmed by developer.android.com
Cause 3 of 4
You ship an APK, not a bundle
1Check
For APKs the setting still creates the symbols file, but it is not uploaded for you.
ls android/app/build/outputs/native-debug-symbols/2Fix
Build with the same setting, then upload native-debug-symbols.zip to the Play Console by hand.
cd android
./gradlew assembleRelease
ls app/build/outputs/native-debug-symbols/*/native-debug-symbols.zip3Verify
The zip exists in the folder; upload it on the app's page in the Play Console.
ls android/app/build/outputs/native-debug-symbols/Confirmed by developer.android.com
Cause 4 of 4
A dependency's libraries are already stripped
1Check
Libraries that arrive ready-made may already have no debug information. Run a build at the info log level with debugSymbolLevel set and look for the line quoted above.
cd android && ./gradlew bundleRelease --info | grep "native debug metadata"2Fix
There is nothing to recover from those libraries. Ask the library owner for an unstripped build if you need names from it.
cd android && ./gradlew bundleRelease --info3Verify
Only the third-party libraries appear in the stripped lines.
cd android && ./gradlew bundleRelease --info | grep "native debug metadata"Confirmed by developer.android.com
How do I stop it coming back?
- Keep debugSymbolLevel in the release build type so every bundle ships with symbols.
- Use SYMBOL_TABLE first; move to FULL only if you need line numbers.
- Keep Dart symbol files from --split-debug-info too; they are separate and are covered by the Flutter obfuscation page.
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 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 fixMobile apps
Android resource linking fails with resource android:attr/lStar not found
error: failed linking references.
The lStar attribute exists only from Android API 31.
2 causes, each with a fix