AppBarn Docs

Appearance

Upload a build ​

Upload an .ipa, .apk or .aab to one App and Environment.

Prerequisites ​

  • active Automation Token with current write authority;
  • configured App and Environment;
  • artifact no larger than 2,147,483,648 bytes.

APK and AAB uploads require explicit identity values:

sh
appbarn upload ./build/app.apk \
  --app-identifier com.example.app \
  --version 1.2.3 \
  --build-number 42

Override defaults when needed:

sh
appbarn upload ./build/app.apk --app <app-uuid> --environment <environment-uuid> \
  --app-identifier com.example.app --version 1.2.3 --build-number 42

The CLI reads an XML IPA Info.plist when available. For any artifact where identity cannot be read, provide the same identity options explicitly. AppBarn computes content hashes and records detected CI provenance.

Expected result ​

The CLI reserves an upload, transfers directly to private R2, finalizes the Build, and prints the ready Build result.

Prompt an agent to upload a build
text
Upload this project's next mobile build to AppBarn using the installed CLI.

Inspect the build scripts and current AppBarn configuration to find the artifact produced by the existing workflow. Confirm the target App and Environment are configured and use `APPBARN_TOKEN` only from a secure environment variable. Upload only a supported `.ipa`, `.apk` or `.aab` file. For Android APK/AAB artifacts, pass the application identifier, version and build number explicitly. For an IPA whose identity cannot be read, pass the same identity values explicitly. Do not print the token or add it to source control.

Before changing build scripts or uploading, ask me any question needed to choose between available artifacts, platforms, App/Environment targets, release identities or build-number sources. If the repository makes one choice clear, use it without asking. Do not fabricate identity values.

After the upload, verify that AppBarn reports a ready Build and summarize its non-secret identity, hash and provenance. Stop and explain the actionable error if the upload fails.

Common failures ​

  • 413: file exceeds the upload cap.
  • 429: Build/storage quota exhausted.
  • 409: reservation/idempotency or Environment lifecycle conflict.
  • parse/identity failure: supply a valid artifact or required explicit identity.