What problem does it solve? EAS cloud and local builds fail with cryptic errors — swallowed messages, lockfile rejections, fingerprint mismatches, gradle crashes — and the official docs rarely cover the actual root cause. This Skill maps eleven real, field-verified failure cases from symptom to root cause to fix, so you stop guessing and start fixing. ## Core Features & Use Cases - Symptom-first casebook: Eleven documented failures (npm ci lockfile drift, .easignore archive bloat, expo-updates fingerprint mismatch, Swift compile errors, Metaspace OOM, gradle cache corruption, swallowed node errors, ExtraTranslation lint, ERESOLVE peer conflicts, Kotlin return-type errors), each with root cause and a repo-committed fix. - Diagnostic toolbox: Decompress brotli EAS logs, keep the local build working directory, replay gradle by hand, and inspect what went into the expo-updates fingerprint. - Environment vs repo triage: A simple rule — if local and cloud both fail, the problem is in the repo; if only one side fails, it is the environment. - Use Case: Your cloud build fails at Configure expo-updates while local works. The Skill points you to stray ios//android/ directories or hand-edited node_modules, and prescribes patch-package plus fingerprint comparison to fix it permanently. ## Quick Start Ask the agent to diagnose your EAS build failure by pasting the error message, for example: my eas build fails with npm error Invalid lock file, find the root cause and fix it.
