app-store-deploy

# App Store Deploy (mobile) ## Overview Mobile does not deploy to a cloud you run — it deploys to **Apple's and Google's stores**, so there is no GCP/AWS split. The CD pipeline builds a signed artifact and uploads it to a test track (TestFlight / Play internal), which is the mobile equivalent of a staged deploy. Read [[ci-cd-pipeline-authoring]] for the workflow naming/dispatch contract; this skill fills in the store steps. **Core principle:** Signing is the hard part, not the upload. Get reproducible, secret-driven signing right and the release is a one-command fastlane lane. ## Pick the boilerplate `search_boilerplate_catalog` → `deploy mobile`. Copy its fastlane config + `deploy-stage/preprod/prod.yml` into the app and set the secrets its README lists. ## Environment mapping - `stage` → internal test track: **TestFlight** (iOS) / Play **internal** track (Android). - `preprod` → **TestFlight external** group / Play **closed** (beta) track. - `prod` → App Store / Play **production** — the workflow file must contain `prod`/`production`/`release` so `trigger_release` dispatches it. ## iOS — TestFlight - Build on a **macOS runner** (`runs-on: macos-14`). - Signing via fastlane **match** (certs/profiles in a private git repo, decrypted with `MATCH_PASSWORD`) — never check certificates into the app repo. - Auth to App Store Connect with an **API key** (`.p8` + key id + issuer id), not an Apple ID password. - Lane: `fastlane build_app` → `upload_to_testflight`. For prod, ...