expo-eas-submit
Skill8 starsChanged 3 months agoMITView on GitHub
App Store Connect and Google Play Console upload flow with EAS Submit, metadata, build-artifact selection, review notes, and phased release. Triggers on eas submit, app store connect, google play, asc api key, service account, metadata, screenshot, phased release, review notes, testflight, internal testing, production submit, release management.
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-buildSkill
- 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
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 86
Add an internal testing group
- Very specific: line 162
Before submit, in eas.json or ASC:
- Distinctive: line 163
Demo account: test username/password
- Distinctive: line 182
Use the ASC API Key (instead of Apple ID/password — no 2FA issues)
- Distinctive: line 184
Phased release: always on (panic rollback)
- Distinctive: line 186
Write the review notes demo path clearly — lowers the reject risk
- Distinctive: line 193
No privacy policy URL → reject (critical for Apple)
≈ “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-submit
A guide to the App Store Connect (iOS) and Google Play Console (Android) submit process with EAS Submit. Metadata management, build-artifact selection, review notes, and phased-release discipline. Build-profile DETAIL lives in expo-eas-build.
What It Does
- Uploading iOS/Android builds with
eas submit - App Store Connect API Key (ASC) and Google Play Service Account setup
- Build artifact selection (latest / specific URL / specific ID)
- Review notes and demo-account management
- Phased release / staged rollout
- Screenshot and metadata upload discipline
Setup
eas submit:configureeas.json Submit Section
{
"submit": {
"production": {
"ios": {
"ascAppId": "1234567890",
"appleTeamId": "ABCDE12345",
"ascApiKeyPath": "./credentials/AuthKey_XXX.p8",
"ascApiKeyId": "XXX",
"ascApiKeyIssuerId": "yyy-yyy-yyy"
},
"android": {
"serviceAccountKeyPath": "./credentials/play-service-account.json",
"track": "internal",
"releaseStatus": "draft",
"rollout": 0.1,
"changesNotSentForReview": false
}
},
"preview": {
"android": { "track": "internal" }
}
}
}iOS Submit Flow
# 1. Upload the latest build
eas submit --platform ios --profile production --latest
# 2. Specific build ID
eas submit -p ios --id <build-id>
# 3. Upload a local IPA
eas submit -p ios --path ./build.ipaASC API Key (recommended)
App Store Connect > Users and Access > Integrations > App Store Connect API:
- Key ID, Issuer ID,
.p8file - Role: App Manager (enough for submit)
Store ascApiKeyPath in eas.json or on the EAS server.
TestFlight Flow
- Submit completes successfully → ASC > TestFlight > Processing
- Answer the compliance questions (encryption usage)
- Add an internal testing group
- Beta Review is required for external testing
Android Submit Flow
eas submit -p android --profile production --latest
eas submit -p android --path ./app.aabService Account Setup
Google Play Console > Setup > API access:
- Create new service account (inside the GCP project)
- Role: Service Account User
- Play Console > Users and permissions > Invite service account
- Permissions: Release manager (submit + manage)
- Download the JSON key →
eas.jsonserviceAccountKeyPath
Tracks
| Track | Purpose | Approval |
| internal | 100 testers, fast | Instant |
| closed (alpha/beta) | Email list | Instant |
| open testing | Public beta | Review required |
| production | All users | Review required |
Staged Rollout
{
"android": {
"track": "production",
"rollout": 0.1, // 10% start
"releaseStatus": "inProgress"
}
}Increase gradually from the console: 0.1 → 0.25 → 0.5 → 1.0.
Metadata Management
store.config.json (Expo store metadata):
{
"configVersion": 0,
"apple": {
"info": {
"en-US": {
"title": "MyApp",
"subtitle": "Productivity for everyone",
"description": "...",
"keywords": ["productivity", "tasks"],
"marketingUrl": "https://myapp.com",
"supportUrl": "https://myapp.com/support",
"privacyPolicyUrl": "https://myapp.com/privacy"
}
},
"copyright": "2026 MyCompany",
"release": {
"automaticRelease": false,
"phasedRelease": true
}
}
}eas metadata:push # send to ASC
eas metadata:pull # fetch the current metadataReview Notes & Demo Account
Before submit, in eas.json or ASC:
- Demo account: test username/password
- Notes: a test path for review (e.g. login → premium feature path)
- Contact info: who to reach if the review team asks
Screenshot Upload
Size requirements (iOS 2026):
- 6.9" iPhone (1320 x 2868)
- 6.5" iPhone (1284 x 2778)
- 12.9" iPad (2048 x 2732)
Android:
- Phone: min 320px, max 3840px
- 7" tablet, 10" tablet
Upload to ASC with
eas metadataor use Fastlane Snapshot. Manual upload is always an option.
Best Practices
- Use the ASC API Key (instead of Apple ID/password — no 2FA issues)
- Service Account role minimum: Release Manager
- Phased release always on (panic rollback)
- Clarify compliance questions first (export compliance, encryption)
- Write the review notes demo path clearly — lowers the reject risk
- Refresh What's New for every release
Common Failure Patterns
- ASC bundle ID doesn't match the build → submit reject
- Service Account is not "Release Manager" → permission denied
- No privacy policy URL → reject (critical for Apple)
- Encryption usage not filled in → stuck in TestFlight
- Wrong screenshot size → upload fails
- Build "Missing Compliance" → set it manually in ASC
Hard Refusal
- Wrong/misleading metadata (false advertising)
- Using another company's/brand's logo or name without permission
- Putting production data in the demo account (the review team sees it)
- A false declaration in the privacy policy
- Hijacking an ASC or Play Console account
Output Format
- Submit command (copy-paste)
- Credentials setup steps
- Track/rollout decision (with rationale)
- Review notes template
- Phased release plan
- Risk: chance of reject, demo account hygiene
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.

