mhmzdev/appflight-cli-docsLight logoAppFlight CLI

appflight.json

Project config file — lives in your Flutter project root alongside pubspec.yaml.

Lives in your Flutter project root alongside pubspec.yaml. Commit it — it's team-shared config.

Full example

{
  "version": 1,
  "projectType": "flutter",
  "apps": {
    "stage": {
      "appflightAppId": "com.myapp.stage",
      "packageName": "com.myapp.stage",
      "apkPath": "build/app/outputs/flutter-apk/app-stage-release.apk"
    },
    "qa": {
      "appflightAppId": "com.myapp.qa",
      "packageName": "com.myapp.qa",
      "apkPath": "build/app/outputs/flutter-apk/app-qa-release.apk"
    },
    "prod": {
      "appflightAppId": "com.myapp",
      "packageName": "com.myapp",
      "apkPath": "build/app/outputs/flutter-apk/app-prod-release.apk"
    }
  },
  "defaultFlavor": "stage"
}

Fields

version

Schema version. Always 1.

projectType

Always "flutter". React Native support is planned.

apps

Map of flavor name → app entry. No-flavor projects have a single "default" entry.

App entry fields:

FieldDescription
appflightAppIdApp identifier on AppFlight (matches packageName)
packageNameAndroid applicationId registered on AppFlight
apkPathRelative path to the built APK from project root

defaultFlavor

Used when appflight upload is run without --flavor. Omitted for no-flavor projects.

No-flavor project

{
  "version": 1,
  "projectType": "flutter",
  "apps": {
    "default": {
      "appflightAppId": "com.mycompany.myapp",
      "packageName": "com.mycompany.myapp",
      "apkPath": "build/app/outputs/flutter-apk/app-release.apk"
    }
  }
}

Custom APK path

apkPath is set automatically by init. If your build produces APKs elsewhere, edit it manually or use --file at upload time:

appflight upload --flavor stage --file path/to/custom.apk
Edit this page on GitHub
📊 analytics
🖥️ Environment Variables