A reference implementation for Flutter CI/CD pipelines using GitHub Actions. This repo demonstrates a branch-based deployment strategy for multi-platform Flutter apps.

Runs on every push to main and on PRs:

• Flutter analyze (static analysis)
• Flutter test (unit tests)

Runs on push to build branch or build-android tag:

• Android: Builds signed AAB and APK, uploads as artifacts
• iOS: Builds signed IPA, uploads as artifact

Runs on push to deploy branch:

• Android: Builds AAB, uploads to Google Play internal testing track
• iOS: Builds IPA, uploads to TestFlight
• macOS: Builds signed app, creates DMG, uploads as artifact
• Windows: Builds release, creates ZIP, uploads as artifact

1. Generate keystore (if you don't have one):

   keytool -genkey -v -keystore upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload

2. Encode keystore to base64:

   base64 -i upload-keystore.jks | pbcopy  # macOS
   base64 upload-keystore.jks | xclip      # Linux

3. Create Play Store service account:

   • Go to Google Play Console → Setup → API access
   • Create or link a Google Cloud project
   • Create a service account with "Release manager" role
   • Download the JSON key file
   • Copy the entire JSON content as the secret value

1. Export certificate from Keychain Access:

   • Open Keychain Access
   • Find your "Apple Distribution" certificate
   • Right-click → Export → Save as .p12
   • Base64 encode: base64 -i Certificates.p12 | pbcopy

2. Download provisioning profile:

   • Go to Apple Developer → Certificates, Identifiers & Profiles
   • Download your App Store distribution profile
   • Base64 encode: base64 -i profile.mobileprovision | pbcopy

3. Create App Store Connect API key:

   • Go to App Store Connect → Users and Access → Keys
   • Generate a new key with "App Manager" access
   • Download the .p8 file (only available once!)
   • Base64 encode: base64 -i AuthKey_XXXXX.p8 | pbcopy
   • Note the Key ID and Issuer ID

Create this file for iOS builds:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>method</key>
    <string>app-store</string>
    <key>teamID</key>
    <string>YOUR_TEAM_ID</string>
    <key>uploadBitcode</key>
    <false/>
    <key>uploadSymbols</key>
    <true/>
</dict>
</plist>

Before using these workflows, update the following:

1. Android package name (line 61):

   packageName: com.example.your_app  # Change to your package name

2. macOS developer name (line 180):

   DEVELOPER_NAME: Your Name  # Change to your developer name

3. macOS/Windows app name (lines 188, 228):

   APP_NAME: YourApp  # Change to your app name

git push origin main

git push origin main:build
# Or for Android only:
git tag build-android && git push origin build-android

git push origin main:deploy
# Or for iOS TestFlight only:
git tag build-ios && git push origin build-ios

Deploy builds automatically increment the build number using:

$(( github.run_number + 100 ))

This ensures build numbers always increase and start above any manual builds you may have done.

MIT - Use freely for your own projects.