Resolving INSTALL_FAILED_INSUFFICIENT_STORAGE errors when deploying apps

When you push an app installation or upgrade through Esper and see INSTALL_FAILED_INSUFFICIENT_STORAGE in the event feed, the device does not have enough free internal storage to complete the installation. This article walks you through how to diagnose the problem and get your deployment back on track.

Why this happens

Android needs temporary space to extract and verify an APK during installation — not just space for the installed app itself. When a device's storage is near capacity, this step can fail. You may notice the install succeeds after a few retries; this happens because Android periodically frees up temporary files, making space available between attempts.

Storage tends to fill up quietly over time — from app caches, system logs, downloaded files, and older app versions. The amount shown on the device itself is often not a reliable indicator of what is actually used. The Esper console gives you the accurate picture.

Step 1: Check storage in the Esper console

Go to Devices & Groups and select the affected device.
Open Device Details and scroll to the Storage section.
Compare the used and available storage against the size of the app you are trying to deploy.

As a general rule, you need at least 2–3 times the APK size available before a reliable installation can complete. If the storage data looks outdated, trigger a manual refresh before reading the values.

Step 2: Free up storage on the device

If storage is near capacity, use one of the following options to free up space before retrying.

Option 1 — Clear app cache remotely

Go to Devices & Groups → select the device → Actions → Clear App Data/Cache. This is the fastest option and works for most apps.

Option 2 — Identify large files using Remote ADB

If you are not sure what is consuming space, use Remote ADB to investigate:

adb shell df -h
adb shell du -sh /sdcard/* | sort -rh | head -20

This shows the largest directories on the device so you can identify and clear what is no longer needed.

Option 3 — Limit app cache accumulation

If a managed browser or data-heavy app is generating large cached files over time, configure the app to limit its cache size, or schedule periodic manual clears through the app's own settings.

Step 3: Retry the deployment

Once you have confirmed sufficient free storage, retry the app deployment from Apps → select the app → Deploy.

To confirm it worked, go to Devices & Groups → device → App Management and verify the new version shows as Installed with no error.

Still seeing the error?

If storage appears adequate but the error persists, collect a bug report from the affected device before reaching out to support — it significantly speeds up the investigation.

To request a bug report: Devices & Groups → device → Logs → Request Bug Report. For detailed instructions, see Logs and Bug Reports.

Once you have the bug report, submit a support ticket and attach it. Include the device model, the app name and version you were deploying, and a note on how many devices are affected.

For a full list of app installation errors and their fixes, see App Installation Troubleshooting.