Flutter release build fails: SigningConfig "release" is missing required property "storeFile"
SigningConfig "release" is missing required property "storeFile".Short answer
Gradle built a release signing config but storeFile came out empty. In a Flutter project that means key.properties was not found at android/key.properties, or it has no storeFile line, or the Gradle code reads a different key name. Fix the file location and its four keys, then run flutter clean and build again.
Fix it fast
1Find out which cause you have
Check that the properties file exists where the Gradle code looks for it, and that all four keys are on separate lines.
ls -l android/key.properties grep -E '^(storePassword|keyPassword|keyAlias|storeFile)=' android/key.properties | sed 's/=.*/=.../'2Match what you see, then jump to its fix
- 1
The file exists, but not at [project]/android/key.properties (for example it sits in the project root or in android/app).key.properties is not in the android folderFix - 2
key.properties is found, but the error still names storeFile.The storeFile line is missing, misspelled or emptyFix - 3
key.properties looks right and is in the right place.The signingConfigs block reads the wrong property nameFix
- 1
What does the error look like?
SigningConfig "release" is missing required property "storeFile".
Cause 1 of 3
key.properties is not in the android folder
1Check
The Flutter template loads rootProject.file("key.properties"), and for a Flutter app the Gradle root project is the android folder. A file anywhere else is simply not found, and the loading code is wrapped in an exists() check, so nothing complains until signing.
ls android/key.properties
find . -name key.properties -not -path "./build/*"2Fix
Move the file to android/key.properties. If you keep it elsewhere on purpose, change the path in the rootProject.file(...) call to match.
mv key.properties android/key.properties3Verify
Clean and build the release bundle again.
flutter clean
flutter build appbundle --releaseConfirmed by docs.flutter.dev
Cause 2 of 3
The storeFile line is missing, misspelled or empty
1Check
Gradle reads the exact property names keyAlias, keyPassword, storeFile and storePassword. A typo such as storefile or store_file returns null, and storeFile then becomes null in the signing config.
cat android/key.properties | sed 's/Password=.*/Password=.../'2Fix
Write the four keys exactly as the Flutter guide shows them. Use a full path for storeFile, and on Windows double the backslashes.
storePassword=<password from keytool>
keyPassword=<password from keytool>
keyAlias=upload
storeFile=/Users/you/upload-keystore.jks3Verify
Run the release build again and confirm signing passes.
flutter build apk --releaseConfirmed by docs.flutter.dev
Cause 3 of 3
The signingConfigs block reads the wrong property name
1Check
In android/app/build.gradle(.kts) look at the release block inside signingConfigs. Each line must read the same key name that the file defines, and storeFile must be turned into a File with file(...).
grep -n -A8 "signingConfigs" android/app/build.gradle.kts android/app/build.gradle 2>/dev/null2Fix
Use the Flutter guide's form, which also yields null instead of a crash when the property is absent.
// android/app/build.gradle.kts
signingConfigs {
create("release") {
keyAlias = keystoreProperties.getProperty("keyAlias")
keyPassword = keystoreProperties.getProperty("keyPassword")
storeFile = keystoreProperties.getProperty("storeFile")?.let { file(it) }
storePassword = keystoreProperties.getProperty("storePassword")
}
}3Verify
Build the release again; the Gradle error should be gone.
flutter build appbundle --releaseConfirmed by docs.flutter.dev
How do I stop it coming back?
- Keep key.properties and the .jks file out of version control, and store a copy of both in a password manager or secret store.
- On a CI server, write key.properties from secrets before the build step, then check the file exists in the same job.
- Run flutter clean after changing Gradle signing settings so cached builds do not hide the change.
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
Android build cannot find the keystore file for signing
Keystore file not found for signing config 'release'
The build was told to sign with a keystore file and no file exists at that path.
3 causes, each with a fixMobile apps
Signing a release build stops with Failed to read key from keystore
Failed to read key from keystore
Gradle opened the signing config but could not get the key out of the keystore.
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 fix