ship-expo-cloud
Skill4 starsChanged 2 days agoMITView on GitHub
EAS cloud build and submit pipeline for the Threadbase iOS app. ONLY invoke this skill when the user explicitly types /ship-expo-cloud. Never trigger automatically on "ship", "TestFlight", or general release requests — those go to /expo-local-ship instead. Before running any EAS command, confirm with the user and wait for explicit approval.
- Reads credentials
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-providerSkill
- expo-local-shipSkill
- integration-by-batchesSkill
- setup-cloudflaredSkill
- ship-fastlaneSkill
- add-provider-mobileSkill
- expo-local-shipSkill
- integration-by-batches-mobileSkill
- setup-cloudflaredSkill
- ship-expo-cloudSkill
- ship-fastlaneSkill
- threadbase-designSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
Before any eas build, run the same gating checks as /expo-local-ship.
- Very specific: line 58
Run both before eas build --profile production.
- Very specific: line 62
If check-build-number.sh auto-bumps app.json, commit the bump before running eas build.
- Very specific: line 92
After running eas build, EAS prints a build URL like:
- Distinctive: line 169
After submission, Apple processes the build.
- Distinctive: line 181
Wait for Apple processing (5-30 min)
- Distinctive: line 190
Add internal testers (your team) or external test groups
- Distinctive: line 226
If you chose Manual Release, go back to App Store Connect and click Release This Version
- Distinctive: line 227
If you chose Automatic Release, it goes live as soon as it's approved
- Very specific: line 245
Read references/troubleshooting.md for common issues like:
- Distinctive: line 255
Use this checklist when doing a production release:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Deploy
End-to-end build and release pipeline for the Threadbase iOS app using EAS (Expo Application Services).
Project Quick Reference
| Key | Value |
| Bundle ID | com.ronenmars.threadbase |
| ASC App ID | 6762130307 |
| EAS Project ID | 35430e75-2718-4261-a46c-d6f6ff1e27c3 |
| Owner | ronenmars |
| Slug | threadbase-mobile |
| Version source | Remote (EAS-managed) |
| Auto-increment | Production builds only |
Workflow Overview
There are four main workflows, each available via CLI or web dashboard:
- Build — compile the app on EAS servers
- Monitor — track build progress and retrieve artifacts
- Submit to TestFlight — send a build to App Store Connect for beta testing
- Release to App Store — promote a TestFlight build to production
The typical release flow is: pre-ship checks -> Build -> Monitor -> Submit to TestFlight -> test -> Release to App Store.
0. Pre-ship checks (mandatory)
Before any eas build, run the same gating checks as /expo-local-ship.
The rules are canonical and shared — see
../_shared/pre-ship-checks.md for the
full rationale and rules.
The two scripts in scripts/ enforce them:
# 1. Branch sanity, no uncommitted app.json, local main synced with origin/main.
./scripts/git-sync-check.sh
# 2. Source signing creds (asc-jwt.sh needs them) then reconcile buildNumber.
source .env.signing
./scripts/check-build-number.shRun both before eas build --profile production. EAS minutes are
expensive — failing fast on a stale base (or a build number that's
already taken in TestFlight) saves a 15-minute wasted cloud build.
If check-build-number.sh auto-bumps app.json, commit the bump
before running eas build. Cloud builds capture the working tree at
build-start time; an uncommitted bump means the version that ships
won't match what's in git.
# After the pre-ship scripts pass and any auto-bump is committed:
eas build --platform ios --profile production1. Build
CLI
# Production build (App Store / TestFlight)
eas build --platform ios --profile production
# Preview build (internal distribution, no App Store)
eas build --platform ios --profile preview
# Development build (dev client with hot reload)
eas build --platform ios --profile development
# Android production build
eas build --platform android --profile productionAfter running eas build, EAS prints a build URL like:
https://expo.dev/accounts/ronenmars/projects/threadbase-mobile/builds/<build-id>Save this URL — it's how you track the build.
Flags worth knowing:
--auto-submit— automatically submit to the App Store when the build finishes--no-wait— start the build and return immediately (don't block the terminal)--message "description"— attach a note to the build for your team--clear-cache— force a clean build (useful when native deps change)
Web Dashboard
- Go to expo.dev -> sign in as
ronenmars - Open project threadbase-mobile
- Click Builds in the sidebar
- Click Build from GitHub or trigger manually
- Select platform (iOS) and profile (production/preview/development)
2. Monitor Build
CLI
# List recent builds (shows status, profile, platform)
eas build:list
# View a specific build by ID
eas build:view <build-id>
# Stream build logs in real time (blocks until complete)
# The URL printed by `eas build` opens the log viewer in browserBuild statuses: new -> in-queue -> in-progress -> finished (or errored/cancelled).
Polling a build until it finishes:
# Check status of the most recent iOS production build
eas build:list --platform ios --status finished --limit 1Web Dashboard
- Go to expo.dev -> threadbase-mobile -> Builds
- Each build shows real-time status, logs, and duration
- Once finished, click the build to download the
.ipa(iOS) or.apk/.aab(Android)
3. Submit to TestFlight
Submitting sends the built .ipa to App Store Connect. From there, Apple processes it (5-30 minutes), and it appears in TestFlight for beta testers.
CLI
# Submit the most recent production iOS build
eas submit --platform ios --profile production --latest
# Submit a specific build by ID
eas submit --platform ios --profile production --id <build-id>
# Submit a specific build by URL
eas submit --platform ios --profile production --url <build-url>The --latest flag grabs the most recent successful build for the given profile and platform.
Combine build + submit in one step:
eas build --platform ios --profile production --auto-submitAfter submission, Apple processes the build. Track processing status in App Store Connect (see web workflow below).
Web Dashboard
Option A — Via Expo Dashboard:
- Go to Builds -> click the finished production build
- Click Submit to App Store (if the button is available)
Option B — Via App Store Connect (manual upload):
- Download the
.ipafrom the Expo build page - Open Transporter app (free from Mac App Store)
- Drag the
.ipainto Transporter and click Deliver - Wait for Apple processing (5-30 min)
Option C — Via App Store Connect web:
- Go to appstoreconnect.apple.com
- Open Threadbase (App ID:
6762130307) - Go to TestFlight tab
- The build will appear once Apple finishes processing
After the build arrives in TestFlight:
- Add internal testers (your team) or external test groups
- For external testing, Apple requires a brief review (~24h first time, faster after)
- Share the TestFlight link with testers
4. Release to App Store (Production)
There is no fully-automated CLI path to the App Store — Apple requires manual metadata review and submission through App Store Connect. Here's the full process:
Pre-submission (CLI can help)
# Verify the build exists and is in "finished" state
eas build:list --platform ios --profile production --status finished --limit 1
# If not already submitted to ASC, submit it
eas submit --platform ios --profile production --latestApp Store Connect (required for all releases)
- Go to appstoreconnect.apple.com
- Open Threadbase -> App Store tab
- Click "+" Version or Platform in the sidebar to create a new version (e.g., 1.1.0)
- Fill in / update:
- What's New — release notes for this version
- Screenshots — required on first release, update if UI changed
- Description, Keywords, Support URL — update if needed
- Build — click the "+" next to Build and select the submitted build
- Under App Review Information, verify contact info and demo account if needed
- Click Submit for Review
Apple review typically takes 24-48 hours. You'll get an email when approved.
After approval:
- If you chose Manual Release, go back to App Store Connect and click Release This Version
- If you chose Automatic Release, it goes live as soon as it's approved
Version Management
EAS handles version auto-increment for production builds (configured in eas.json). The version source is remote, meaning EAS tracks the current build number server-side.
# Check current version info
eas build:version:get --platform ios
# Manually set version (rarely needed)
eas build:version:set --platform ios --build-number <N>Troubleshooting
Read references/troubleshooting.md for common issues like:
- Build failures (provisioning, signing, native deps)
- Submission rejections (metadata, compliance, screenshots)
- TestFlight processing stuck
- Version/build-number conflicts
Full Release Checklist
Use this checklist when doing a production release:
- All tests pass locally and in CI
- Pre-ship checks (
./scripts/git-sync-check.shthensource .env.signing && ./scripts/check-build-number.sh). See../_shared/pre-ship-checks.md. - Commit any auto-bumped
app.jsonbefore triggering EAS - Version bump (if needed beyond auto-increment)
eas build --platform ios --profile production- Monitor build until
finished eas submit --platform ios --profile production --latest- Wait for Apple processing in App Store Connect
- Verify build in TestFlight — install and smoke test
- Create new version in App Store Connect
- Write release notes, attach build, update screenshots if needed
- Submit for App Review
- After approval: release (manual or automatic)
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.

