Building a Flutter app

For documentation on building Flutter projects using the settings in Codemagic UI, please refer to Building Flutter apps via UI.

With codemagic.yaml, you can use Codemagic to build, test and publish Flutter apps, widgets, Flutter or Dart packages. The necessary build commands go under scripts in the overall architecture of the codemagic.yaml file. You can find some examples for building the most common types of Flutter projects below.

Exporting configuration from UI

You can get started with YAML easily if you have an existing project set up in Codemagic UI.

  1. Navigate to your app settings.
  2. In the Configuration as code section on the right sidebar, click Download configuration.

The YAML feature currently has the following limitations:

  • Exporting configuration from UI is supported for Flutter-based Android, iOS and web apps.
  • The exported configuration is not identical to the settings in the UI and lacks the configuration for some features, such as Stop build if tests fail and publishing to Codemagic Static Pages.

Building with YAML

In order to use codemagic.yaml for build configuration in Codemagic, it has to be committed to your repository. The file must be located in the root directory of the repository. When detected in the repository, codemagic.yaml is automatically used for configuring builds that are triggered in response to the events defined in the file. Any configuration in the UI is ignored.

In order to use codemagic.yaml for manual builds, you must select the workflow to build from codemagic.yaml:

  1. Navigate to your app settings and click Start new build.
  2. In the specify build configuration popup, select the branch where your codemagic.yaml file is located.
  3. If a codemagic.yaml file is found in that branch, you can click Select workflow from codemagic.yaml.
  4. Then select the workflow to build from the Select workflow from codemagic.yaml dropdown.
  5. Finally, click Start new build to start the build.

Android builds

Set up local properties

- echo "flutter.sdk=$HOME/programs/flutter" > "$FCI_BUILD_DIR/android/"

Building .apk

- flutter build apk --release

Building universal .apk(s) from existing app bundle(s) with user-specified keys

If your app settings in Codemagic have building Android App Bundles enabled, we will automatically include a script for generating a signed app-universal.apk during the YAML export. If you are creating a YAML file from a scratch, add the following script to receive the .apk file(s):

- android-app-bundle build-universal-apk \
  --bundle 'project_directory/build/**/outputs/**/*.aab' \
  --ks /tmp/keystore.keystore \
  --ks-key-alias $FCI_KEY_ALIAS \
  --key-pass $FCI_KEY_PASSWORD

Please make sure to wrap the --bundle pattern in single quotes. If --bundle option is not specified, default glob pattern **/*.aab will be used.

More information about Android code signing can be found here.

Codemagic uses the android-app-bundle utility to build universal .apk files from Android App Bundles.

iOS builds

Building an unsigned application .app

- flutter build ios --debug --no-codesign

Building a signed iOS application archive .ipa

Codemagic uses the xcode-project to prepare iOS application code signing properties for build.
- xcode-project use-profiles
- xcode-project build-ipa --workspace ios/Runner.xcworkspace --scheme Runner

Read more about the different schemes in Apple’s documentation.

Note: If you are using Flutter version 1.24.0-6.0 or higher, the recommended command for building an .ipa archive is flutter build ipa as shown below. Read more about it in Flutter’s documentation.

- xcode-project use-profiles
- flutter build ipa --export-options-plist=/Users/builder/export_options.plist

Web builds

- name: Build web
  script: |
    flutter config --enable-web
    flutter build web --release
    cd build/web
    7z a -r ../ ./*    

Testing, code signing and publishing a Flutter app

To test, code sign and publish a Flutter app:

  • Testing examples for a flutter app can be found here.
  • All iOS and Android applications need to be signed before release. Different script examples are available here.
  • All generated artifacts can be published to external services. The available integrations currently are email, Slack, Google Play and App Store Connect. It is also possible to publish elsewhere with custom scripts. Script examples for different options are available here.