Skip to content

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.

AI prompt — Upload an existing build (Copilot, Codex, Cursor)
text
Inspect the existing build workflow and locate a real IPA, APK or AAB. Confirm configured App/Environment UUIDs and APPBARN_TOKEN without printing it. Run appbarn upload with explicit app identifier, version and build number for APK/AAB (and IPA when identity extraction fails). Ask only if artifact, target or identity is ambiguous. Preserve the build workflow, verify the resulting ready Build with appbarn builds list and report its identity, SHA-256 and provenance.

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.