appforshare
Upload iOS (.ipa) and Android (.apk) builds to AppForShare from your terminal or CI and get an install link and QR code page for your testers.
export APPFORSHARE_TOKEN=afs_... # Dashboard > Settings > API tokens (Pro and Team)
npx appforshare upload build/MyApp.ipa --notes "Fixes the login crash"
The command prints the install link. --json prints { url, slug, name, version, expiresAt, readiness, findings, channel }.
In GitHub Actions the link is also written to the step outputs url, slug, readiness and, with --channel,
channel_url.
Large builds upload in 32 MB chunks and resume after a dropped connection.
Commands
| Command | What it does |
|---|---|
appforshare upload <file> | Upload a build (.ipa, a zipped .app, .apk or .aab), print its install link and store readiness status. --password, --email <up to 5>, --notes (or --comment), --channel |
appforshare builds | List recent builds (--platform ios|android, --app <bundle id>, --project <id>, --limit <n>) |
appforshare latest | Install link of the newest build (same filters, plus --channel <name>) |
appforshare promote <id|slug> --channel <name> | Put a build into a channel (Beta, Live); doing it for an older build rolls the channel back |
appforshare feedback-task <feedback id> | Add a task from a tester feedback report to its project's task board (Team) |
appforshare activity [--project <id>] [--kind <kind>] | Workspace activity, newest first: uploads, channels, feedback, tasks, release checklist, link controls (Team) |
appforshare send-feedback <feedback id> --to <linear|jira> | Make an issue in the workspace's Linear or Jira from a tester feedback report, with its screenshots (Pro and Team) |
appforshare checklist <id|slug> | Release checklist of a build, open blockers and whether the gated channel (Live) takes it (Team) |
appforshare link <id|slug> [--pause|--resume] [--stop <date|off>] [--max-installs <n|off>] | Pause an install link, stop it after a date or cap its installs (Pro and Team) |
appforshare testflight <url|off> --channel <name> --app <bundle id> | TestFlight public link for a channel: iPhone and iPad visitors go to TestFlight, Android visitors get the newest APK (Pro and Team) |
appforshare info <id|slug> | Version, size, installs, link, why testers' phones may refuse it, and every store readiness finding with its fix |
appforshare installs <id|slug> | Who installed a build: device, OS, country and the tester when known |
appforshare email <id|slug> --to <emails> | Email the install link to up to 5 addresses; nobody gets the same build twice (Pro and Team) |
appforshare channel-address <address> --channel <name> --app <bundle id> | Give a channel its own link, /c/; the old one keeps redirecting for 30 days (Pro and Team) |
appforshare delete <id|slug> --yes | Delete a build; it can be restored from the dashboard for 7 days |
appforshare feedback [id|slug] [--status open|resolved|all] | Tester feedback from install pages, newest first, with device and a dashboard link |
appforshare whoami | Account, role and plan of the token |
All commands take --json.
Channels (Beta, Live)
npx appforshare upload app-release.apk --channel beta
npx appforshare promote 12345 --channel live
A channel has one link and QR code that never change and always open the newest build put into it, on iPhone or Android. The channel is created the first time you use its name. Pro and Team plans.
Fail the pipeline on store readiness
npx appforshare upload app-release.apk --fail-on blocked
The build is uploaded and its link works either way. With --fail-on blocked the command exits with code 2 when
the store readiness check finds a blocker (for example a debuggable build, the debug signing key, an old target
API level or iOS SDK). --fail-on review also fails on findings that need a look. The check is guidance about
current App Store and Google Play rules, not a promise of approval.