Error map
INSTALL_FAILED_INSUFFICIENT_STORAGE INSTALL_FAILED_INSUFFICIENT_STORAGE: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
Android · layer 1, On your device
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
You’re accessing blob/queue data with Microsoft Entra ID, but the identity has only management roles (Owner/Contributor) — not a…
QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota
localStorage/sessionStorage is full (about 5 MB per origin) or storage is disabled.
Azure Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature (AuthenticationFailed)
The storage request’s signature or SAS token is invalid — wrong/rotated account key, expired SAS, or clock skew.
INSTALL_PARSE_FAILED_NO_CERTIFICATES / App not installed as package appears to be invalid
The APK isn’t signed (or the signature is invalid for this Android version), so it can’t be installed.
adb: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set
The phone hasn’t accepted your computer’s RSA key for USB debugging yet.
MySQL ERROR 126 (HY000): Incorrect key file for table; try to repair it
MySQL can’t use a table’s index file — usually a full tmp disk during a query, or MyISAM corruption.
Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition
The kubelet couldn’t mount one of the pod’s volumes, so the pod stays in ContainerCreating.
PersistentVolumeClaim stuck in Pending (no persistent volumes available / waiting for first consumer)
The PVC hasn’t been bound to a volume, so pods using it can’t be scheduled.
MySQL ERROR 1114 (HY000): The table 'x' is full
MySQL couldn’t extend the table — disk full, a size limit, or a MEMORY table hitting max_heap_table_size.
ERROR: could not extend file "base/…": No space left on device
The disk holding the PostgreSQL data directory (or WAL) is full.
StorageAccountAlreadyTaken: The storage account named x is already taken
Storage account names are globally unique across Azure; another customer (or you elsewhere) already uses the name.
INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries
The APK contains native (.so) libraries only for CPU architectures the device doesn’t support — e.g. x86 emulator with arm-only l…
Two steps away (35)
AWS S3: AccessDenied (403) when calling GetObject / PutObject
An IAM policy, bucket policy, ACL/ownership setting, Block Public Access or KMS key policy denied the S3 request.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
Azure: AuthorizationFailed — The client does not have authorization to perform action
The signed-in identity (user, service principal or managed identity) lacks an Azure RBAC role for that action on that scope.
net::ERR_BLOCKED_BY_CLIENT
A browser extension (ad blocker, privacy tool) blocked the request.
net::ERR_CONNECTION_REFUSED (This site can't be reached — refused to connect)
The browser reached the host but nothing was listening on that port.
net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found)
DNS couldn’t resolve the hostname in the browser.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
A Conditional Access policy requires MFA, but the sign-in flow (often a script, legacy client or ROPC password grant) can’t compl…
AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match
AWS rejected the request signature — wrong secret key, wrong region, clock skew, or a presigned URL used differently from how it…
Android: INSTALL_FAILED_UPDATE_INCOMPATIBLE
An app with the same package name but a different signing key is already installed on the device.
error: gpg failed to sign the data — fatal: failed to write commit object
Commit signing is enabled but GPG couldn’t sign — no TTY for the passphrase, wrong key, or agent not running.
INSTALL_FAILED_OLDER_SDK / INSTALL_FAILED_DEPRECATED_SDK_VERSION
The device’s Android version is lower than the app’s minSdk (OLDER_SDK), or the app’s targetSdk is too old for this Android versi…
INSTALL_FAILED_TEST_ONLY: installPackageLI
The APK is marked testOnly (built by Android Studio’s Run button), so normal installs refuse it.
INSTALL_FAILED_USER_RESTRICTED: Install canceled by user (Xiaomi/MIUI, Oppo, Vivo)
The phone’s manufacturer layer blocked installs over USB — Xiaomi/MIUI, Oppo/ColorOS and Vivo require extra developer settings.
adb: no devices/emulators found / error: device not found
adb can’t see any connected device or running emulator.
error: object file .git/objects/x is empty / fatal: loose object is corrupt
The local Git object database is corrupted — usually after a crash, disk full or sync tool interference.
sqlite3.DatabaseError: database disk image is malformed
The SQLite file is corrupted.
Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another
A ReadWriteOnce volume (EBS, Azure Disk, PD) is still attached to another node, so the new pod on a different node can’t use it.
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
Kubernetes: CreateContainerConfigError — secret / configmap not found
Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…
invalid mount config for type "bind": bind source path does not exist
A -v/--mount or Compose volume points at a host path that doesn’t exist (from the Docker daemon’s point of view).
Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.
Permission denied writing to a mounted volume inside a Docker container
The process inside the container runs as a user (UID) that doesn’t own the bind-mounted host folder, so reads/writes fail with EA…
Docker Desktop: Mounts denied: The path is not shared from the host and is not known to Docker
Docker Desktop (macOS) can only bind-mount folders listed under Settings → Resources → File sharing.
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
HTTP 503 Service Unavailable
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.
MySQL ERROR 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.
FATAL: sorry, too many clients already / remaining connection slots are reserved for non-replication superuser connections
PostgreSQL reached max_connections.
FATAL: too many connections for role "x"
The role reached its per-role CONNECTION LIMIT (often set by hosting providers or free tiers).
TypeError: 'str' object is not callable
You used parentheses on something that isn’t a function — often a variable shadowing a built-in.
BucketAlreadyExists: The requested bucket name is not available
S3 bucket names are global across all AWS accounts, and someone else already uses this one.
CloudFormation: Resource ... already exists (AlreadyExists / already exists in stack)
The template tries to create a resource with a fixed name that already exists — created manually, by another stack, or left over…
no matching manifest for linux/arm64/v8 in the manifest list entries
The image has no build for your CPU architecture — typically pulling an amd64-only image on an Apple Silicon Mac or ARM server.
AAPT: error: resource android:attr/lStar not found
A dependency (androidx.core 1.7+) uses an attribute from Android 12 (API 31), but your module compiles against an older compileSd…
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException