ship-expo-cloudlisted

# 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: 1. **Build** — compile the app on EAS servers 2. **Monitor** — track build progress and retrieve artifacts 3. **Submit to TestFlight** — send a build to App Store Connect for beta testing 4. **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`](../_shared/pre-ship-checks.md) for the full rationale and rules. The two scripts in `scripts/` enforce them: ```bash # 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.sh