Flutter run fails with INSTALL_FAILED_INSUFFICIENT_STORAGE on the Android emulator
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]Short answer
The emulator's own data partition is full, not your Mac. Remove old copies of the app with adb uninstall, then wipe the AVD's data in Device Manager. If it fills again, edit the AVD and raise Internal Storage under Show Advanced Settings. Check the emulator's free space with adb shell df first.
Fix it fast
1Find out which cause you have
See how much space the emulator's /data partition has left.
adb shell df -h /data2Match what you see, then jump to its fix
- 1
df shows /data nearly full on a fresh AVD, or Use% stays high after a wipe.The AVD's Internal Storage is too small for the appFix - 2
The AVD has been used for many builds of different apps and space has fallen over time.Old builds and data of apps fill the AVDFix - 3
Space is low even though few apps are installed.The AVD storage area needs a clean resetFix
- 1
What does the error look like?
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
Cause 1 of 3
The AVD's Internal Storage is too small for the app
1Check
The AVD sets the non-removable storage through the Internal Storage property.
adb shell df -h /data2Fix
Stop the emulator. In Android Studio open Device Manager, choose Edit this AVD, click Show Advanced Settings, and raise Memory and Storage > Internal Storage. Then start it again.
# no command: Device Manager > Edit this AVD > Show Advanced Settings
# > Memory and Storage > Internal Storage3Verify
Run the app again and check the free space.
flutter run
adb shell df -h /dataConfirmed by developer.android.com
Cause 2 of 3
Old builds and data of apps fill the AVD
1Check
Each installed app keeps its code and data in the AVD storage area. List third-party packages to see what is installed.
adb shell pm list packages -32Fix
Uninstall the packages you do not need, including earlier builds of your own app.
adb uninstall com.example.myapp3Verify
Free space should rise, and flutter run installs.
adb shell df -h /data
flutter runConfirmed by developer.android.com
Cause 3 of 3
The AVD storage area needs a clean reset
1Check
The AVD keeps user data, installed apps and settings in a dedicated storage area on your computer. Wiping it returns the AVD to its new state.
adb shell pm list packages -32Fix
In Device Manager, open the AVD's Menu and choose Wipe Data. This deletes everything you installed in that AVD.
# no command: Device Manager > AVD Menu > Wipe Data3Verify
Start the AVD and run the app.
flutter runConfirmed by developer.android.com
How do I stop it coming back?
- Give each AVD a larger Internal Storage value when you create it, instead of the default.
- Delete AVDs you no longer use.
- Uninstall test apps from the emulator when you finish with a project.
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