Menu

Individual skill

flutter-store-cd

0upvotes

Use when setting up or debugging continuous delivery of a Flutter app to the App Store and Google Play with GitHub Actions - a tag that builds and uploads both apps, Android upload-keystore signing, iOS manual signing with a certificate and provisioning profile on a macOS runner, App Store Connect API keys, Play service accounts, build numbers, or when a store upload or CI build fails (draft app errors, SDK version 409, altool timeouts, codesign hangs, pods refusing a profile). Also covers the first-release traps around the pipeline - first manual Play upload, Play App Signing fingerprints for Firebase and App Check, and submitting the first subscriptions.

skills/flutter-store-cd/SKILL.md

Read pinned source

Source commit addd6d85e5d92bacc1e8bf14c23c585380a4b371

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
14
Repository last updated
Oct 30, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

You are setting up, or fixing, the pipeline that takes a Flutter app from a git
tag to TestFlight and Google Play. The design in one line: **push a `v*` tag,
two independent workflows build, sign and upload each platform; nothing else
triggers a store build.**

Two ready workflows sit next to this file, written in full from a production app.
Copy them to `.github/workflows/`, then set the `env:` block at the top of each:

- [`templates/android-play.yml`](templates/android-play.yml): ubuntu, signs an
  App Bundle, uploads it to Play
- [`templates/ios-testflight.yml`](templates/ios-testflight.yml): macOS, archives
  and signs an IPA, uploads it to TestFlight

The rest of this skill is the reasoning behind them and the traps each line