Store Release — App Store + Google Play first submission

Everything needed to take a Flutter app from "builds locally" to "submitted for review" on both stores. Covers the one-time account/console setup, the metadata + screenshots upload via fastlane, and the gotchas that block a first release specifically.

Two-pipeline model. Keep internal distribution and store release separate:

• deploy.sh → internal builds, no fastlane (iOS TestFlight via no-codesign archive + xcodebuild -exportArchive + altool; Android Firebase App Distribution). See the appdist skill.
• prod.sh → store releases, through fastlane (iOS App Store via deliver; Android Google Play via supply).

This skill owns the prod.sh / fastlane half and the submission checklist.

When to use

• Submitting an app to the App Store or Play Store for the first time.
• Wiring up fastlane deliver (iOS) / supply (Android) for metadata + screenshots.
• A first submission got rejected and you need the known-blocker list.
• Generating ready-to-paste prompts for an AI agent to drive each release step.

Quick start

# 1. Copy templates into the project
cp -r templates/ios/*       ios/fastlane/
cp -r templates/android/*   android/fastlane/
cp templates/ios/Gemfile    ios/Gemfile
cp templates/android/Gemfile android/Gemfile
cp assets/.env.example      .env.prod      # then fill with REAL values (gitignored)

# 2. Ruby env (system ruby 2.6 is usually broken — use Homebrew ruby)
export PATH="/opt/homebrew/opt/ruby/bin:$PATH"
export LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8   # REQUIRED or deliver crashes on non-ASCII metadata

# 3. iOS App Store listing (metadata + screenshots, no binary)
cd ios && bundle install && bundle exec fastlane release_listing

# 4. Android Play Store (build AAB + upload to internal track + metadata)
cd android && bundle install && bundle exec fastlane internal

What's in this skill

Golden rules

1. Never commit secrets. .env.prod, .p8, .p12, .mobileprovision, .jks/keystores, and service-account JSON stay gitignored. Keep them in a private mirror (e.g. a separate .app_dist repo), not the app repo.
2. App record must exist before the first upload. ASC API keys cannot POST /v1/apps (403) — create the app once in the App Store Connect web UI. Same for Play: create the app in the Play Console first.
3. UTF-8 locale is mandatory for deliver if any locale has non-ASCII text.
4. The App Store version string must equal the build's CFBundleShortVersionString or the build won't attach.
5. Use Homebrew ruby + bundler + bundle exec — the macOS system ruby gem set is usually incomplete.

See references/first-release-checklist.md for the detailed walkthrough.