Quick Start

The typical workflow from authentication to your first mobile build upload and app management.

Get up and running with the BuildShare CLI in three simple steps.

Run the login command to authenticate your machine. In interactive terminals, it prompts for your BuildShare email and password:

buildshare login

Alternatively, supply an API token inline or via the BUILDSHARE_TOKEN environment variable:

BUILDSHARE_TOKEN=<your-token> buildshare login

Upload your compiled Android APK or iOS IPA directly. BuildShare shows real-time progress and generates a public OTA install link immediately:

buildshare upload ./app-release.apk

You can target a specific app ID and provide release notes directly:

buildshare upload ./app.ipa --app my-app-id --notes "Release 2.4.0 preview"

Once uploaded, the CLI prints the shareable OTA installation URL and terminal QR code.

List all applications registered in your active workspace along with their package names and platform identifiers:

buildshare app list

To list recent builds uploaded for a specific application:

buildshare build list --app <app-id>

Next Steps

Explore the full command references and CI/CD automation guides:

Inspect all upload flags, changelog options, and JSON outputs.

Set up automated builds in GitHub Actions, GitLab CI, or Bitbucket.

Learn about global flags, environment variables, and exit codes.