AppBarn Docs

Appearance

Quick start ​

Use AppBarn to upload one build and confirm it is retained outside CI.

Prerequisites ​

  • an AppBarn Workspace, Project, App and Environment;
  • an Automation Token scoped to the target Project or App;
  • Node.js 22+.

Steps ​

  1. Configure the API and target resources:
sh
appbarn config set api https://api.app-barn.com
appbarn config set app <app-uuid>
appbarn config set environment <environment-uuid>
  1. Export the token without putting it in command history:
sh
export APPBARN_TOKEN='<automation-token>'
  1. Upload an IPA, APK or AAB:
sh
appbarn upload ./build/app.apk \
  --app-identifier com.example.app \
  --version 1.2.3 \
  --build-number 42
  1. List retained builds:
sh
appbarn builds list

Expected result ​

The upload returns a ready Build with parsed identity, SHA-256 and provenance. builds list returns the same Build.

Prompt an agent to set up a first build
text
Set up AppBarn for this repository and upload one existing mobile build.

First inspect the project to identify its package manager, Node.js version, mobile platform, build command and output artifact. Install the official `appbarn-cli` npm package if it is not already available, requiring Node.js 22 or later. Configure `https://api.app-barn.com` plus the target App and Environment UUIDs. Use an Automation Token only through `APPBARN_TOKEN`; never place it in configuration, source files, command arguments or logs. Upload the selected `.ipa`, `.apk` or `.aab`, passing Android identity values explicitly when required, then use `appbarn builds list` to confirm the ready Build is retained.

Before making choices that the repository does not answer, ask me which AppBarn App and Environment to use, which artifact to upload when several are available, and how I want the Automation Token supplied. Ask any other integration question that has multiple valid answers. Do not invent IDs, release identity values or secrets.

Keep the existing build flow intact, make the smallest necessary changes and report the verified Build identity, SHA-256 and detected provenance without exposing credentials.

Common failures ​

  • 401: token missing, expired or revoked — create/use a current Automation Token.
  • 403/404: token scope or current App Manager authority does not cover the target — verify Workspace/Project/App selection.
  • 409: idempotency or lifecycle conflict — do not reuse an upload identity for different bytes.
  • 413: artifact exceeds the 2 GiB upload cap.
  • 429: Workspace quota is exhausted — remove retained data or request more capacity.