- Home
- Skills
- Mobile Development
- expo-build-triage
Works with the AI Agents you already use
Expo Build Triage
Diagnose failed Expo and React Native builds: reads the build log and project config, classifies the failure, applies verified fixes, and escalates cleanly when it needs hands-on debugging.
Free
expo-build-triage
Example session with this skill installed
My EAS build failed with a Gradle error. Here is my package.json and the log showing 'duplicate-class' errors for some native libraries. How do I fix this?
- Read your context and instructions
- Compiled the expo-build-triage
The build failed during the native Android compilation phase. The log indicates a duplicate-class error caused by two native dependencies shipping the same .so or Java classes, which usually happens when multiple libraries include the same underlying SDK.
Build Diagnosis & Fix
| Metric | Details |
|---|---|
| SDK Version | Expo SDK 50 |
| Failing Phase | Native Build (gradlew) |
| Error Signature | mergeDebugNativeLibs / DuplicateRelativeFileException |
| Root Cause | Conflict between expo-notifications and a third-party analytics library |
To resolve this, we need to instruct Gradle to pick the first occurrence of the conflicting library rather than failing. Modify your app.json to use expo-build-properties:
{
"expo": {
"plugins": [
[
"expo-build-properties",
{
"android": {
"packagingOptions": {
"pickFirst": [
"**/libcrypto.so",
"**/libssl.so"
]
}
}
}
]
]
}
}
Next steps
- Run
npx expo-doctorto ensure no other version conflicts exist. - Run
npx expo prebuild --cleanlocally to verify the config plugin applies without errors. - Trigger a new build with
eas build --profile previewto verify the fix in the cloud environment.
Connects securely to your tools. The creator never sees your data.
About this skill
Expo Build Triage is a diagnostic skill for failed Expo and React Native builds. Give your agent a build log and it works from evidence: runs expo-doctor first, matches the error against a known signature table (dependency drift, Gradle native-lib conflicts, Kotlin mismatches, CocoaPods failures, config plugin errors, signing and credential problems, EAS-cloud-only drift, SDK-upgrade breakage), applies one fix at a time with verification, and stops after three failed attempts instead of guessing. Includes a dedicated SDK upgrade mode. Free — and when a build needs hands-on native debugging, it hands off cleanly instead of burning your build minutes.
Cannot fix builds requiring hand-written native code changes in bare-workflow projects, lost Android keystores, or revoked Apple certificates — it escalates these instead of guessing. Diagnosis quality depends on having the complete build log; a truncated log means a provisional diagnosis.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Requires
Permissions
File Scopes
Needs to read build logs and project config files, and run expo-doctor and build commands in the terminal. Never touches signing credentials or keystores.