Fix Android Emulator “Not Enough Space” Error (installDebug Failed)

By -

Fix Android Emulator “Not Enough Space” Error (installDebug Failed)



If you are running a React Native app and see this error when executing npm run android, you are not alone.

Execution failed for task ':app:installDebug'.
...
java.io.IOException: Requested internal only, but not enough space

This error usually means one thing:

🚨 Your Android Emulator is out of storage

💡 Root Cause

By default, Android Virtual Devices (AVD) are created with very limited internal storage (often 2GB–6GB). Over time, this space gets filled by:

  • Debug APK installs
  • Gradle build artifacts
  • System updates and cache

Eventually, there is no space left to install your app.

✅ My Fix (Works Immediately)

The most effective solution is to increase the emulator storage size.

  1. Open Android Studio
  2. Go to Device Manager
  3. Edit your emulator (or create a new one)
  4. Click Show Advanced Settings
  5. Set Internal Storage to 16 GB
  6. Save and restart the emulator

After increasing to 16GB, the issue disappears.

⚡ Alternative Quick Fix

If you need a quick temporary fix:

  • Wipe emulator data (Device Manager → Wipe Data)
  • Uninstall the app manually:
adb uninstall your.package.name

However, these are temporary. The real fix is increasing storage.

🧠 Pro Tips

  • Always allocate at least 12GB–16GB for development AVDs
  • Avoid using snapshots (they can preserve “full disk” state)
  • Clean builds occasionally:
cd android
./gradlew clean

✅ Conclusion

If you see:

Requested internal only, but not enough space

It is not a code issue — it is your emulator running out of disk space.

Fix: Increase AVD internal storage to 16GB.

This is the most reliable and permanent solution.

❤️ Support This Blog

If this post helped you, you can support my writing with a small donation. Thank you for reading.

Coffee ☕ Thanks 🙏 Extra Support ❤️

Comments

Post a Comment

Popular posts from this blog

fixed: embedded-redis: Unable to run on macOS Sonoma

By -
Image
Issue you might see below error while trying to run embedded-redis for your testing on your macOS after you upgrade to Sonoma. java.lang.RuntimeException: Can't start redis server. Check logs for details. Redis process log: at redis.embedded.AbstractRedisInstance.awaitRedisServerReady(AbstractRedisInstance.java:70) at redis.embedded.AbstractRedisInstance.start(AbstractRedisInstance.java:42) at redis.embedded.RedisServer.start(RedisServer.java:9) Solution use the latest one: https://mv   ...
Read more

Copying MDC Context Map in Web Clients: A Comprehensive Guide

By -
Image
Introduction In distributed systems, maintaining context across microservices is crucial for effective logging and tracing. The Mapped Diagnostic Context (MDC) in logging frameworks like Logback or Log4j allows developers to propagate contextual information such as request IDs, user IDs, or correlation IDs across threads and services. When using web clients to make outgoing requests, it's essential to propagate the MDC context map to ensure consistency and traceability. This guide will provide   ...
Read more

Reset user password for your own Ghost blog

By -
Image
If you do not config mail up for your ghost blog, it maybe a big problem once you lost your user password. however, methods are always more than problems. We can fix it up by reset it. 1. Find out your database name in your ghost config, it is maybe in config.production.json   "database": {     "client": "mysql",     "connection": {       "host": "localhost",       "user": "ghost-452",       "password": "dade1b0565f2585e07c7",       "database": "ghost_production_acm" 2. Use mysql to reset the password. mysql -u root -p Enter the password for root account. mysql> use ghost_production_acm; mysql> select * from users; ghost use bcrypthash for the password. You can get bcrypt hash string from http://bcrypthashgenerator.apphb.com/ mysql>update users set password=' $2b$10$PaL8tKcU4i0CsjRrM6BhROVQMwwLFw2HSx/kWlAUgja23fNllc2Fy' where ...
Read more