Flutter Build

Flutter allows you to build cross-platform mobile apps from a single codebase. This recipe demonstrates how to build iOS and Android apps using Flutter, including dependency installation and build compilation.

Flutter iOS Build YAML

name: Flutter iOS Build
platform: flutter

environment:
  flutter: "3.24.0"

triggers:
  - push
  - pull_request

steps:
  - name: Install dependencies
    run: flutter pub get

  - name: Build iOS
    run: flutter build ios

Flutter Cross-Platform Build

name: Flutter Mobile Build
platform: flutter

environment:
  flutter: "3.24.0"

triggers:
  - push
  - pull_request

steps:
  - name: Install dependencies
    run: flutter pub get

  - name: Build Android
    run: flutter build apk

  - name: Build iOS
    run: flutter build ios

Build Workflow

The typical Flutter build workflow includes:

1. Dependency Installation: flutter pub get resolves all Pub dependencies specified in pubspec.yaml
2. iOS Build: flutter build ios generates an iOS app bundle
3. Android Build: flutter build apk generates an Android APK

Key Points

Flutter is Pre-Installed on the Build Machine

FVM is pre-installed and manages Flutter SDK installation automatically. Simply set environment.flutter to a version (e.g., 3.24.0), a channel (e.g., stable, beta, master), or fvm to read from .fvmrc, and the agent will install it automatically. Once installed, Flutter and Dart are available directly on PATH — use flutter and dart in your run: commands.

• Correct: flutter pub get, flutter build ios
• Previously: fvm flutter pub get, fvm flutter build ios (no longer required)

• pubspec.yaml: Your Flutter project’s manifest file, similar to Package.swift for native Swift or package.json for Node.js
• pub get: Downloads and installs all dependencies from pub.dev
• Platform-specific builds: Flutter can generate both iOS and Android builds from the same source code
• .fvmrc file (optional): Commit this at your repository root to pin the Flutter SDK version; if you set environment.flutter: fvm, the agent will read the version from your .fvmrc file

Building an iOS IPA from Flutter

When auto-signing is fully configured, you can build and export an iOS IPA directly from Flutter:

name: Flutter Build IPA
platform: flutter

environment:
  flutter: "3.41.8"

triggers:
  - push

steps:
  - name: Get dependencies
    run: flutter pub get

  - name: Build iOS
    run: flutter build ios --release --no-codesign

  - name: Create IPA
    run: flutter build ipa --release

Auto-Signing for Flutter IPA Builds

When Apple auto-signing is configured at both the workspace level (API key) and app level (bundle identifier + signing type), RunnerHub automatically passes the generated ExportOptions.plist to your flutter build ipa command via the --export-options-plist flag. You do not need to add this flag manually.

To override with your own provisioning configuration, pass an explicit --export-options-plist=/path/to/your.plist and the agent will not inject (your file takes precedence).

To opt out of signing entirely (for testing purposes), use --no-codesign and the agent will skip injection.

Collecting Flutter Build Artifacts

You can collect build outputs from your Flutter builds:

name: Flutter Build with Artifacts
platform: flutter

environment:
  flutter: "3.24.0"

triggers:
  - push

steps:
  - name: Install dependencies
    run: flutter pub get

  - name: Build iOS
    run: flutter build ios

  - name: Build Android
    run: flutter build apk

artifacts:
  - build/ios/iphoneos/**/*.app
  - build/ios/archive/**/*.xcarchive
  - build/app/outputs/**/*.apk