AppForShareGet started

Docs

Coming from Zunoy AppShare or ShareIPA

Most of what you use on Zunoy AppShare has a place here: the upload line in your pipeline, Quick Releases, Persistent URLs, the UDID list, the release forum, testing credentials and notifications. This guide maps each one and says which plan it needs.

  1. Step 1, Pro and Team

    Replace the appshare CLI line

    In each pipeline (GitHub Actions, GitLab, Bitrise, fastlane, CircleCI, Jenkins), replace npm install -g zunoy-appshare-cli and appshare <file> --app-id <slug> with one AppForShare upload. Make an API token in Dashboard, Settings, API tokens and store it as APPFORSHARE_TOKEN. Release notes, a channel and a readiness gate are flags of the same command, and the GitHub Action, the fastlane plugin and the Gradle plugin do the same without a shell step.

    # before
npm install -g zunoy-appshare-cli
appshare build/app-release.apk --app-id my-app

# after
npx --yes appforshare upload build/app-release.apk --channel beta --notes "$(git log -1 --pretty=%B)"
    CI guides for each service

  2. Step 2, Every plan, channels on Pro and Team

    Quick Release and Persistent URL

    A Quick Release is one build with one link: on AppForShare that is any upload, with its install page, QR code and optional password. A Persistent URL that always serves the latest build is a channel such as Beta or Live: one link and QR code per channel, iPhones get the iOS build and Android phones the Android build. Pick your own address such as /c/acme-beta, and put an older build back if a release goes wrong.

    There is no import from AppShare, so upload again the builds your testers still need. Old AppShare links keep working there until they expire.

    npx appforshare upload app.ipa --channel beta
npx appforshare channel-address acme-beta --channel beta --app com.example.shop
    Custom channel address

  3. Step 3, Every plan, registration on Pro and Team

    UDID list to Devices

    Import your UDID list into Devices (one UDID per line with an optional name, or Apple's device file). On Pro, send iPhone testers the onboarding link of the iOS project: their device is saved and, with an App Store Connect connection, registered on Apple in one click. The ad hoc profile can be made again with every enabled device. On Team, Hands free registers the device, remakes the profile and starts the GitHub build.

    npx appforshare devices import udids.txt
    iOS device registration

  4. Step 4, Every plan, replies on Team

    Release forum to the feedback inbox

    Testers press Send feedback on the install page, or from inside the build through the in-app feedback link, with screenshots and no SDK. Reports land in one inbox. On Team you reply to a tester and they get one email in their language with a link to answer back; on Pro and Team they can rate each build from 1 to 5 stars. Send a report to Linear or Jira on Pro and Team.

    Reply to testers and star ratings

  5. Step 5, Pro and Team

    Testing credentials

    Add up to 3 test logins with a note to a build or a channel. Testers see them on the install page with copy buttons only after the page password or an access code is accepted. They are stored encrypted and never sent in emails or webhooks.

    printf '%s' "$TEST_PASSWORD" | npx appforshare link <build> --test-login [email protected] --test-password-stdin --test-note "Staging"
    Test accounts on the install page

  6. Step 6, Pro and Team

    Notifications

    In Dashboard, Integrations, add Telegram with a bot token from @BotFather and a chat id, or Slack, Microsoft Teams, Google Chat, Discord or a signed webhook. Telegram gets new builds, installs and feedback; the others get more events, such as store review states.

    Webhooks and integrations

  7. Step 7, Pro and Team

    Links that no longer expire

    AppShare links end after 15 to 90 days by plan. Upload a build once on Pro or Team and its link stays live while you subscribe, with no download cap per app. If you cancel, links follow Free rules and stay live 7 more days. Send testers the new link or the channel link once, and they keep it.

    Plans and limits

Questions

Can I import my builds from Zunoy AppShare?
No. There is no export from AppShare that we can read, so upload again the builds your testers still need. Old links keep working on AppShare until they expire.
Is there a drop in replacement for the appshare CLI?
No. Replace the one appshare line with npx appforshare upload, the GitHub Action or the fastlane plugin. Uploads with a token are on Pro and Team.
I used ShareIPA without an account. What changes?
Without an account AppForShare takes builds up to 50 MB for 3 days with a private manage link and no password. A free account takes 150 MB for 7 days with a password and .aab uploads; Pro takes 2 GB with links that stay while you subscribe.
Do my testers need an account?
No. They open the link on the phone and install. On Team, invited testers of a private project get an emailed link, still with no account.
Can my team members join for free?
Free and Pro have one seat. Team includes 5 seats, then $6 a month each. Testers never take a seat.

Weighing the two first? Read AppForShare vs Zunoy AppShare and ShareIPA. For the upload commands, see Upload from CI.