expo-eas-build
Skill8 starsChanged 3 months agoMITView on GitHub
iOS and Android build profiles with EAS Build, credentials management, build cache, secrets, and monorepo support. Triggers on eas build, eas.json, build profile, credentials, provisioning profile, keystore, push certificate, service account, build cache, eas secret, monorepo, development build, preview build, production build.
- Installs packages
In this repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-automationSkill
- consultingSkill
- contentSkill
- customer-successSkill
- data-analyticsSkill
- designSkill
- design-tokensSkill
- developmentSkill
- devopsSkill
- ecommerceSkill
- emailSkill
- expo-app-configSkill
- expo-config-pluginSkill
- expo-dev-clientSkill
- expo-eas-submitSkill
- expo-eas-updateSkill
- expo-modulesSkill
- expo-notificationsSkill
- expo-orchestratorSkill
- expo-prebuildSkill
- expo-routerSkill
- expo-troubleshootingSkill
- financeSkill
- frontend-tasteSkill
- marketingSkill
- market-researchSkill
- mobileSkill
- pentest-adSkill
- pentest-apiSkill
- pentest-bizlogicSkill
- pentest-bugbountySkill
- pentest-cicdSkill
- pentest-cloudSkill
- pentest-credentialsSkill
- pentest-ctfSkill
- pentest-detectionSkill
- pentest-engagementSkill
- pentest-exploit-chainSkill
- pentest-forensicsSkill
- pentest-llmSkill
- pentest-malwareSkill
- pentest-mobileSkill
- pentest-opsec-evidenceSkill
- pentest-orchestratorSkill
- pentest-privescSkill
- pentest-reconSkill
- pentest-reportSkill
- pentest-socialSkill
- pentest-stigSkill
- pentest-threat-modelSkill
- pentest-webSkill
- pentest-wirelessSkill
- productivitySkill
- productSkill
- salesSkill
- security-checkSkill
- securitySkill
- seo-crawl-budgetSkill
- seoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 198
Keep the keystore backup offline (loss = a new package name)
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
expo-eas-build
A guide to profile discipline, credentials management, and the build process for EAS Build. Scoped to eas.json configuration, iOS provisioning + push cert, Android keystore + service account, secrets, and monorepo support. Store-submit DETAIL lives in expo-eas-submit.
What It Does
eas.jsonprofile architecture (development / preview / production)- iOS credentials: provisioning profile, distribution cert, push cert
- Android credentials: keystore, upload key, FCM service account
- Build cache, environment variables, EAS Secrets
- Build hooks (
eas-build-pre-install,eas-build-on-success) - Monorepo (
pnpm/yarn workspaces/turborepo) support
Setup
npm install -g eas-cli
eas login
eas whoami
eas init # assigns the project ID
eas build:configure # eas.json startereas.json Template
{
"cli": { "version": ">= 7.0.0", "appVersionSource": "remote" },
"build": {
"base": {
"node": "20.11.0",
"env": { "EXPO_PUBLIC_APP_ENV": "base" }
},
"development": {
"extends": "base",
"developmentClient": true,
"distribution": "internal",
"ios": { "simulator": true },
"channel": "development"
},
"preview": {
"extends": "base",
"distribution": "internal",
"android": { "buildType": "apk" },
"channel": "preview",
"env": { "EXPO_PUBLIC_APP_ENV": "preview" }
},
"production": {
"extends": "base",
"autoIncrement": true,
"channel": "production",
"env": { "EXPO_PUBLIC_APP_ENV": "production" }
}
},
"submit": { "production": {} }
}Profile Strategy
| Profile | Distribution | Purpose | Device |
| development | internal | Dev client, JS debug, hot reload | Device/sim |
| preview | internal | QA/stakeholder test (IPA/APK) | Device |
| production | store | App Store / Play Store | Device |
iOS Credentials
eas credentials # interactive menu
eas credentials -p ios # iOS onlyEAS manages:
- Distribution Certificate (.p12)
- Provisioning Profile (.mobileprovision)
- APNs Push Key (.p8)
Apple account connection:
eas credentials --platform ios
# Apple ID + app-specific password or ASC API keyASC API Key (recommended for CI):
# App Store Connect > Users > Keys > Generate
# Use the .p8 file instead of EAS_APPLE_APP_SPECIFIC_PASSWORDAndroid Credentials
eas credentials -p androidEAS manages:
- Keystore (build signing) — loss = the app can't be updated
- FCM Service Account (push)
- Google Play Service Account JSON (for submit)
Keystore backup:
eas credentials -p android
# Download → Keystore → back up keystore.jks (offline + encrypted)Running a Build
eas build --profile development --platform ios
eas build --profile preview --platform all
eas build --profile production --platform android
# Local build (for CI/CD)
eas build --local --profile preview --platform android
# Specific commit/branch
eas build --profile production --message "v1.2.0 release"EAS Secrets & Environment
eas secret:create --scope project --name SENTRY_AUTH_TOKEN --value xxx
eas secret:list
eas secret:delete --id <id>eas.json env:
"production": {
"env": {
"EXPO_PUBLIC_API_URL": "https://api.example.com",
"SENTRY_DSN": "$SENTRY_DSN"
}
}
EXPO_PUBLIC_*is embedded in the client. NEVER prefix secret values withEXPO_PUBLIC_.
Build Hooks
package.json:
{
"scripts": {
"eas-build-pre-install": "echo 'pre-install hook'",
"eas-build-post-install": "patch-package",
"eas-build-on-success": "node ./scripts/notify-slack.js"
}
}Monorepo
eas.json:
{
"build": {
"production": {
"cache": { "key": "mono-v1" },
"node": "20.11.0"
}
}
}.easignore (prevent unneeded files from bloating the upload):
node_modules/
.git/
apps/web/
packages/web-only/For pnpm/yarn workspaces, cli.appVersionSource: "remote" and the package.json > workspaces path must be correct.
Best Practices
appVersionSource: "remote"— version centralized on EASautoIncrement: true— buildNumber/versionCode automatic- The production profile must not have
developmentClient - Keep the keystore backup offline (loss = a new package name)
- Push cert/key renewal: test in production, then distribute
Common Failure Patterns
bundle identifierchange → provisioning profile invalidversionCodenot incremented → Play Store rejects- iOS push cert missing → notifications don't work (
expo-notifications) - EAS Secret with the
EXPO_PUBLIC_prefix → leaks to the client - Missing
.easignorein a monorepo → bloats the upload, slows the build
Hard Refusal
- Using another developer's keystore/provisioning profile without permission
- Bundle ID hijacking (impersonating an existing app)
- Connecting to an unauthorized Apple ID/Google Play account
- Signing with a forged certificate
Output Format
eas.jsonsnippet (per profile)- Credentials flow (who manages it, how it's verified)
- Build command (copy-paste)
- Risks: keystore backup, cert renewal
- Next step:
expo-eas-submit(store upload) orexpo-eas-update(OTA)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

