Error map
Resources$NotFoundException android.content.res.Resources$NotFoundException: Resource ID #0x7f...
Android · layer 1, On your device
Centre: this error. First ring: errors it is linked with (7). 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 (7)
Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage
The kubelet removed the pod because its node ran short of memory or disk.
Error creating: pods is forbidden: exceeded quota: compute-resources, requested: limits.memory=1Gi, used: ..., limited: ...
The namespace’s ResourceQuota doesn’t have room for the new pod’s requests/limits (or object count).
pods is forbidden: failed quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory
A ResourceQuota on the namespace covers CPU/memory, so every pod must declare those requests/limits — and this one doesn’t.
ResourceNotFound: The Resource 'Microsoft.X/...' under resource group 'y' was not found
The specific resource doesn’t exist in that resource group/subscription — wrong name, group or subscription, or it was deleted.
AAPT: error: resource x (aka y) not found — Android resource linking failed
A layout, manifest or style references a resource (drawable, string, style, attribute) that doesn’t exist in the module or its de…
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…
Execution failed for task ':app:mergeDebugResources'. > Duplicate resources
Two resource files define the same name and type in the same configuration (e.g. ic_logo.png and ic_logo.xml).
Two steps away (19)
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
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.
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
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.
VcpuLimitExceeded: You have requested more vCPU capacity than your current vCPU limit
Your account’s On-Demand (or Spot) vCPU quota for that instance family and region is used up.
error: Metrics API not available / HPA: unable to get metrics for resource cpu
metrics-server isn’t installed or isn’t working, so kubectl top and CPU/memory HorizontalPodAutoscalers have no data.
ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate
An Azure Resource Manager (ARM/Bicep/Terraform) deployment failed; the inner error under “details” has the real cause.
ResourceGroupNotFound: Resource group 'x' could not be found
The resource group doesn’t exist in the subscription the command or deployment is using.
MissingSubscriptionRegistration: The subscription is not registered to use namespace 'Microsoft.X'
The resource provider (Microsoft.Web, Microsoft.ContainerService, …) isn’t registered for the subscription.
Gradle: Could not resolve all files for configuration / Could not resolve dependency
Gradle couldn’t download a dependency — wrong coordinates/version, missing repository, offline mode, or network/proxy issues.
Manifest merger failed: android:exported needs to be explicitly specified
Targeting Android 12 (API 31)+ requires `android:exported` on every activity, service or receiver that has an intent-filter.
Duplicate class X found in modules A and B
Two dependencies ship the same class — typically old Android Support libraries mixed with AndroidX, or Kotlin stdlib-jdk7/jdk8 ve…
Gradle: Unsupported class file major version / Android Gradle plugin requires Java 17 to run
The JDK running Gradle doesn’t match what the Gradle version or Android Gradle Plugin (AGP) supports.
Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
The Gradle wrapper JAR (gradle/wrapper/gradle-wrapper.jar) is missing or corrupt.
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…
Failed to find target with hash string 'android-34' / Failed to install the following Android SDK packages as some licences have not been accepted
Gradle needs an SDK platform/build-tools that isn’t installed, or the licences haven’t been accepted on this machine.
Dependency 'androidx.x:1.y' requires libraries and applications that depend on it to compile against version 34 or later of the Android APIs
A library needs a higher compileSdk than your module uses (checkAarMetadata task).
Cannot fit requested classes in a single dex file (# methods: 65536 > 65536) — mergeDex failed
The app exceeds the 64K method reference limit of a single DEX file and multidex isn’t enabled (minSdk below 21).
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException