Bitrise
Add a Script step after the build/export step. Store APPBARN_TOKEN as a protected Secret and IDs as normal environment variables.
sh
npm install --global appbarn-cli
appbarn config set api https://api.app-barn.com
appbarn config set app "$APPBARN_APP_ID"
appbarn config set environment "$APPBARN_ENVIRONMENT_ID"
appbarn upload "$BITRISE_APK_PATH" --app-identifier "$APPBARN_APP_IDENTIFIER" --version "$APPBARN_VERSION" --build-number "$APPBARN_BUILD_NUMBER"Use the appropriate Bitrise artifact path for IPA/AAB outputs. AppBarn detects Bitrise provenance from standard CI environment variables.
AI prompt — Add a Bitrise upload (Copilot, Codex, Cursor)
text
Inspect bitrise.yml and existing mobile export steps. Add an AppBarn CLI Script step after the selected IPA/APK/AAB is produced, using the actual Bitrise artifact path. Configure the API and real App/Environment UUIDs, read APPBARN_TOKEN from a Bitrise Secret and supply non-secret Android identity fields when needed. Preserve the current workflow and native provenance. Ask about missing paths or targets, never log secrets, and validate the configuration.Common failures
If the artifact path is empty, place the upload step after the platform export step. Never print the token while debugging.