ship
/ship
Wysyła aplikację Expo lub React Native do sklepów przez lokalne cele buildu, np. TestFlight czy Play, po sprawdzeniu renderu.
- Autor
- andriiklymiuk ↗
- Repozytorium
- corgi ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wysyła aplikację Expo lub React Native do sklepów przez lokalne cele buildu, np. TestFlight czy Play, po sprawdzeniu renderu.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when shipping an Expo/React Native app to the stores via the repo's LOCAL build targets: \"ship it\", \"make ship\", \"build and submit to TestFlight/Play\", \"push a release to the App Store\", \"cut a build\", \"release the app\", \"upload the binary\". Gates on the mobile skill's render first. NOT for device verification, IAP metadata (purchases), or remote EAS cloud builds.
Jak działa
- Overview
- Before you ship
- The shell + locale rule
- Version bump - once
- Drive it
- Verify by ground truth (not the exit code)
- See also
Podgląd SKILL.md
---
name: ship
description: "Use when shipping an Expo/React Native app to the stores via the repo's LOCAL build targets: \"ship it\", \"make ship\", \"build and submit to TestFlight/Play\", \"push a release to the App Store\", \"cut a build\", \"release the app\", \"upload the binary\". Gates on the mobile skill's render first. NOT for device verification, IAP metadata (purchases), or remote EAS cloud builds."
---
# Ship a local build to the stores
Read `../_shared/conventions.md` first (finish what you start, attribution, unattended runs).
**Done when:** a new IPA/AAB is on disk and the submit log says "Submitted" for each store asked for.
## Overview
Ship = the repo's local prod build+submit target (`make ship`, or `make localIosProd` +
`localAndroidProd`) → clean prebuild → IPA/AAB → `eas submit` to TestFlight + Play. A
build compiling ≠ shipped. **Ground truth = a new IPA/AAB on disk + a "Submitted…" line**,
never the exit code. Long + unattended → background + poll.
## Before you ship
- **Render gate (`mobile` skill).** Native-invisible change (shader, particles, 3D scene,
Skia) compiles + ships magenta / square / blank. Drive on device + read the screenshot
first. Green build ≠ verified build.
- Tests + lint/types green. A ship is no place to find a broken bundle.
- `df -h` first - a local iOS archive writes DerivedData + archive + IPA (10 GB+); low disk
kills `pod install` / the archive mid-run with a misleading error.
## The shell + locale rule
Run the build in a **non-login** shell that **also exports the locale**:
```
nohup bash -c 'export LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8; make <ship-target>' > build/ship.log 2>&1 &
```
- `bash -lc` (login) puts a broken rbenv Ruby on PATH → `pod install` dies with a
misleading CocoaPods `visionos` error at prebuild. So: non-login.
- But a non-login shell drops the profile's locale → empty `LANG`/`LC_ALL` →
`Encoding::CompatibilityError` ("CocoaPods requires UTF-8"). So: export it.
- **And it bites one level down:** `eas build --local` runs its own nested prebuild +
`pod install` inheriting the parent env. A Makefile that sets `LANG` *inline* for its
own prebuild step is necessary but not sufficient - if the ambient shell's `LANG` is
empty, EAS's internal pod install dies the same way while the Makefile's succeeded.
Always export in the parent. (Check first: `echo "LANG=$LANG"` - empty is the tell.)
## Version bump - once
`make ship` bumps the marketing version (and EAS bumps iOS buildNumber / Android
versionCode per attempt) first, then builds. **If the build dies after the bump, the
version is bumped but unshipped - don't run `make ship` again** (it double-bumps). Re-run
the build+submit targets directly (`make localIosProd && make localAndroidProd`) - they
don't bump - reusing the already-bumped version.
## Drive it
1. **Background + poll** - there's no foreground tool for 20-40 min, and the `nohup … &`
wrapper "completes" the instant it backgrounds (any task-runner marks that done) - so
there is **no completion event for the real build**. Poll the log:
```
until grep -qiE "BUILD SUCCEEDED|BUILD FAILED|Submitting|successfully uploaded|Submitted your app|error:" build/ship.log; do sleep 25; done
```
Watch the phases: pods → archive/Gradle → IPA/AAB exported → `eas submit` → Apple/Google
ingest ("Waiting for submission to complete" can sit minutes - normal).
2. **stopShip escape hatch** - to abort mid-build, kill the build processes (a `stopShip`
make target, or `pkill -f "xcodebuild|gradle|eas build|eas submit|fastlane"`). The
detached `nohup` build is not a tracked task - `pkill` it, don't wait.
## Verify by ground truth (not the exit code)
- **iOS:** a new `*.ipa` (fresh timestamp) + `✔ Submitted your app to Apple App Store
Connect!` / `successfully uploaded to App Store Connect`. Apple processes ~5-10 min after.
- **Android:** a new `*.aab` + `✔ Submitted your app to Google Play Store!`. Play submits
land as a **draft** release by default (`changes_not_sent_for_review` / draft status) -
you promote it in Play Console; "submitted" ≠ "released".
- **`build/.submit-skipped`** (or the warning line) - a Makefile `eas build … || (test -f
ipa)` fallback + `tee`'d logs report exit 0 while a submit was skipped. If that file is
non-empty, the upload did not happen - upload by hand (Transporter / `make submitIos`).
- **A build that compiles + uploads can still die at launch** - native version/ABI skew
(`DYLD Symbol not found`) shows in neither build nor upload. Install + open the binary
once; if it bounces, it's dep-version skew (pin exact, see `mobile`), not app code.
## See also
- **`mobile` skill** - the device-driving loop + the full gotcha list (the render gate this
skill leans on, plus the dyld-skew / disk / autolinking traps a ship hits).
- **`purchases` skill** - store IAP + metadata (separate from the binary submit).
- `expo:*` plugin skills (when installed) - EAS / SDK specifics.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · andriiklymiuk/corgi | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| namedtoaster/the-last-mile | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| zahidakhyar/skills | 100 | MIT |
| NolwennD/gabier | 100 | Apache-2.0 |
| mgiovani/cc-arsenal | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ba308095ca96 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100eas-app-stores
Buduje i wysyła aplikacje iOS i Android przez EAS do TestFlight, App Store i Google Play: eas.json, pipeline'y wydań, podpisywanie, wersje, zgłoszenia i metadane sklepu. - 90purchases
Zarządza zakupami w aplikacji i metadanymi w sklepach dla aplikacji Expo lub React Native oraz konfiguracją RevenueCat. - 90mobile
Buduje, naprawia i wydaje aplikacje mobilne na Expo, React Native, Androida, iOS lub Flutter, od podpisów po Play Console i TestFlight. - 100mobile
Weryfikuje zmiany w aplikacji mobilnej Expo i React Native na prawdziwym urządzeniu, emulatorze lub symulatorze: zrzuty ekranu, sterowanie przez Maestro oraz lokalne buildy iOS i Android z wysyłką do TestFlight i Play. - 100eas-monorepo-release
Prowadzi przez wysyłkę aplikacji Expo z dużego monorepo do TestFlight i App Store przez EAS, gdy build lub submit się nie udaje. - 100expo-eas-submit
Pomaga przy wysyłce aplikacji do App Store Connect i Google Play Console przez EAS Submit: metadane, wybór artefaktu buildu, notatki do recenzji i wydanie fazowe.