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.
Prompt an agent to add Bitrise upload
text
Add an AppBarn upload Script step to this Bitrise workflow.
Inspect `bitrise.yml`, the existing build/export steps and their output variables. Add the script after the selected IPA, APK or AAB is produced. Install `appbarn-cli`, configure the API origin plus App and Environment UUIDs, and upload the actual Bitrise artifact path. Store `APPBARN_TOKEN` as a protected Bitrise Secret; use normal environment variables for non-secret target IDs and Android application identity, version and build number. Preserve Bitrise-provided provenance and do not log the token.
Before editing, ask me which workflow, export artifact and App/Environment to use when they are not clear. Ask which Bitrise variable should supply the artifact path or which source should supply Android identity if more than one valid option exists. If the protected token has not been configured, tell me the required variable name and ask me to add it without exposing its value.
Validate the workflow syntax and summarize the required variables, step placement and artifact path.Common failures
If the artifact path is empty, place the upload step after the platform export step. Never print the token while debugging.