@buildtree/cli
v0.3.1
Published
Share Android and iOS builds with testers: upload an .apk or .ipa, get an install link and QR code. Works with Expo, React Native, Flutter and native apps, locally or in CI.
Maintainers
Readme
buildtree CLI
Share Android and iOS builds with testers from your terminal. buildtree uploads an .apk or .ipa to buildtree and gives you an install link and a QR code. Testers open the link on their phone and tap Install. No store review, no TestFlight, no Google accounts.
Works with Expo, React Native, Flutter, and native Android and iOS apps, locally or in CI.
npm install -g @buildtree/cli
buildtree login
buildtree upload ./app-release.apk --env dev✔ Uploaded. Build id 7f3c2a91-... (com.example.app v1.4.0 build 42)
Pinned URL https://buildtree.sh/install/7f3c2a91-...
Folder URL https://buildtree.sh/install/folder/my-app/dev (always-latest checkpoint)
(QR code for the pinned URL)Requires Node 18.19 or later. Node 20 or 22 is recommended. Run without installing with npx @buildtree/cli <command>.
Why buildtree
- An install link and QR code for every build. Scan it from the terminal or send the link in Slack.
- A folder for every branch.
--branch feature/paymentsgives that branch its own always-latest link, so QA can test a pull request before it merges. Leave out--branchand the upload becomes the environment's latest build. - iOS without TestFlight. Ad hoc
.ipainstalls over the air, with a built-in flow to collect tester device IDs (UDIDs). - Tester feedback with screenshots, sent from the install page and listed per build.
- Any build source. Your laptop,
eas build --local, Fastlane, Gradle, Xcode or GitHub Actions. buildtree distributes builds; it does not run them.
Commands
| Command | What it does |
|---|---|
| buildtree login | Sign in through the browser. The token is stored locally. |
| buildtree upload <file> | Upload an .apk, .aab or .ipa and print the install links and QR code. |
| buildtree build [platform] | Run the build command from buildtree.config.json. |
| buildtree publish [platform] | build then upload in one step. |
| buildtree list [--project <slug>] | List projects, or the builds in a project. |
| buildtree link --build <id> | A temporary download URL for a build. |
| buildtree delete-project <slug> | Delete a project and its builds. |
Upload options: --project <slug>, --env <name>, --branch <name>, --release <tag>. In a terminal the CLI asks for anything you leave out; in CI pass them all.
Full reference: buildtree.sh/docs/cli
Build config
buildtree build and buildtree publish run whatever command you declare, then upload the file it produces:
{
"builds": {
"android": {
"command": "cd android && ./gradlew assembleRelease",
"artifact": "android/app/build/outputs/apk/release/app-release.apk"
},
"ios": { "command": "fastlane build_ios", "artifact": "build/App.ipa" }
}
}Save it as buildtree.config.json in your project root. Expo projects with an eas.json work with no config (eas build --local).
Framework guides: Expo · React Native · Flutter · iOS distribution
CI
Create an API token in the dashboard and set it as BUILDTREE_TOKEN:
- run: npx @buildtree/cli upload app-release.apk --project my-app --env dev --branch "$GITHUB_HEAD_REF"
env:
BUILDTREE_TOKEN: ${{ secrets.BUILDTREE_TOKEN }}Full workflow, including iOS and a pull request comment with the QR code: GitHub Actions guide
| Variable | Purpose |
|---|---|
| BUILDTREE_TOKEN | API token. Overrides the stored login. |
| BUILDTREE_API_URL | API base URL. Defaults to https://buildtree.sh. |
AI coding agents
Claude Code, Codex, Gemini CLI and Cursor can run the same flow through the buildtree MCP server: "set up buildtree for this app and give me a QR code for an Android build." It shares this CLI's login. Setup guide
Links
- Quickstart
- Share an app with testers
- Compare with TestFlight, Firebase App Distribution, Diawi and EAS
- Migrate from Firebase App Distribution
- Pricing: free tier included
- Support: [email protected]
MIT licensed.
