Skip to content
Get a quote

Android install errorAndroid: “INSTALL_FAILED_INSUFFICIENT_STORAGE”

Running the app from Android Studio, Flutter, React Native or adb install fails with INSTALL_FAILED_INSUFFICIENT_STORAGE. The device has no room for the new build. On an emulator this is common: its data partition is small, and every debug build, cache and old app you installed stays on it.

Short answer

Check the free space first with adb shell df /data. On an emulator, wipe its data from the Device Manager (or start it with -wipe-data), and if it fills up again, give it more internal storage in the AVD’s advanced settings. On a phone, uninstall the old copy of the app and free some space. Also check your build size: a debug APK with every ABI and large assets can be much larger than the release build.

Where the space went, and the fix

  1. 01

    An emulator full of old builds and data

    “The virtual device preserves the app and its state data across restarts in a user data disk partition (userdata-qemu.img).” Android Developers, Start the emulator from the command line

    The emulator keeps installed apps, caches and files between runs. After weeks of debug installs it runs out. Wipe it from the Device Manager menu, or from the command line.

    emulator -list-avds
emulator @Pixel_8_API_35 -wipe-data

  2. 02

    An emulator with too little internal storage

    “The AVD has a dedicated storage area on your development machine. It stores the device user data, such as installed apps and settings, as well as an emulated SD card.” Android Developers, Create and manage virtual devices

    If a wiped emulator fills up again quickly, its data partition is too small for the app. Edit the AVD in the Device Manager and raise internal storage under the advanced settings, or create a new AVD with more. The setting is stored as disk.dataPartition.size in the AVD’s config.ini; wipe the data after changing it so the new size applies.

    adb shell df /data
# in ~/.android/avd/Pixel_8_API_35.avd/config.ini
disk.dataPartition.size=8G

  3. 03

    A phone that is nearly full

    On a real device, uninstall the previous copy of the app (adb uninstall with your package name), then clear space in Settings. An install needs free space beyond the APK’s own size, so a phone with a little space left can still fail.

    adb uninstall com.example.myapp
adb install -r build/app/outputs/flutter-apk/app-debug.apk

  4. 04

    Your computer’s disk is full

    “the emulator checks for sufficient free disk space on startup and doesn't start unless at least 5 GB is free.” Android Developers, Troubleshoot known issues with Android Emulator

    The emulator’s storage is a file on your computer. If your own disk is nearly full, the emulator can fail to start or to grow. Free space on the computer, and delete AVDs you no longer use.

Checked against the vendor’s docs on : Android Developers: Start the emulator from the command line (-wipe-data, -partition-size); Android Developers: Create and manage virtual devices; Android Developers: Troubleshoot known issues with Android Emulator.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: Android “SDK location not found” · Android “Execution failed for task” · Android “Duplicate class found in modules”

Questions

More on this error

Will users see this error?

Users installing from Google Play see the Play Store’s own out-of-space message instead. This code is what adb and the IDE show while you develop. If your app is large, a release build as an Android App Bundle lets Play deliver only the parts each phone needs.

Does wiping the emulator delete my code?

No. It resets the virtual phone: installed apps, their data and settings. Your project files are on your computer and are not touched.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.

Describe your problem All fixes