appflight_cli 0.2.1 
appflight_cli: ^0.2.1 copied to clipboard
mhmz.devAppFlight CLI — upload APKs from your terminal or CI pipelines without the Play Store.
AppFlight CLI #
Upload APKs to AppFlight from your terminal or CI pipelines — no Play Store review, no waiting.
Installation #
dart pub global activate appflight_cli
Make sure ~/.pub-cache/bin is on your PATH, then:
appflight --help
Quick Start #
# 1. Log in with your AppFlight API key
appflight login
# 2. Initialise a project (creates appflight.json)
appflight init
# 3. Upload a build
appflight upload
No flavors? appflight init prompts for your package name and you're done.
Flavored app? Pass --flavor stage (or whichever flavor) to upload.
Commands #
| Command | Description |
|---|---|
appflight init |
Create appflight.json in the current project |
appflight login |
Save API credentials to ~/.appflight/credentials.json |
appflight logout |
Remove saved credentials |
appflight whoami |
Print the currently authenticated user |
appflight upload |
Upload an APK and notify testers |
Releasing a New Version #
Manual publish — no CI, no Changesets, no auto-bump. Keep it simple until the CLI warrants more.
- Bump
versionin bothcli/pubspec.yamlandcli/lib/src/version.dart(they must stay in sync — the--versionflag reads from the Dart constant, not the pubspec). - Add an entry to
cli/CHANGELOG.md. - From
cli/, rundart pub publish.
Documentation #
Full docs, CI/CD guides, and environment variable reference:
app-flight.com/docs
Issues #
Found a bug or have a question? Open an issue in the docs repo:
github.com/mhmzdev/appflight-cli-docs/issues
Metadata
Publisher
Weekly Downloads
Metadata
AppFlight CLI — upload APKs from your terminal or CI pipelines without the Play Store.
Homepage
Repository (GitHub)
View/report issues
License
unknown (license)
Dependencies
args, cli_util, dio, io, path, pub_semver, yaml
