Builds Distribution

From your pipeline
to every tester’s phone.

Upload an iOS or Android build from CI, choose who gets it and let testers install with one tap. No store review, no shared download folders, no outdated builds in chat threads.

iOS & Android · Included in every plan · Hosted in Switzerland

Ship a beta in seconds, not in a release cycle

Get each build to the right people while the change is still fresh, then collect their feedback in the same place.

One endpoint · .ipa & .apk

Upload straight from CI

Send the binary from any pipeline. Appelium reads the app identifier, version, build number, minimum OS version and SDK from the build itself, so there is nothing to fill in by hand.

Private or public

The right build for the right people

Organise testers into groups such as Internal or Beta Testers. Keep groups private for invited members, or open a public link when anyone should be able to install.

Email · Install page · QR code

One tap to the latest version

Notify testers by email with the version, release notes and an install link. On a desktop, a QR code opens the install page on their phone.

Testers found something? Let them send it with in-app bug reporting, including screenshots, logs and device details.

Know exactly what your testers are running

Every upload becomes a numbered build with the details you would otherwise dig out of the binary.

  • Provisioning profile, decoded. See the profile type, team, expiration date and entitlements of every iOS build.
  • Availability at a glance. iOS builds show when they expire with their profile; Android builds do not expire.
  • See what was installed. Download counts per build show whether a new version actually reached your testers.
  • Testers without Dashboard access. The Tester role can install distributed builds and nothing more.
Demo Shop · iOScom.appelium.demo
Illustrative iOS builds with availability and downloads
BuildAvailabilityDownloads
4.3.0 (418)#418 · Today, 09:41Expires in 11 months37
4.3.0 (417)#417 · Yesterday, 17:12Expires in 11 months52
4.2.0 (391)#391 · Oct 6, 14:03Expired 3 days ago64
No more “the link doesn’t work”.

Spot expired builds before testers do, and distribute a build signed with a renewed profile.

Illustrative data

Add one step to your pipeline

Works with any CI provider, from GitHub Actions to a self-hosted runner. Upload, then distribute to the groups you choose.

1 · Upload the build
curl -X POST \
  -H "X-Appelium-Token: $APPELIUM_TOKEN" \
  -H "X-Appelium-Application-Alias: demo-ios" \
  --data-binary @DemoShop.ipa \
  https://api.appelium.com/v2/builds
2 · Distribute & notify testers
curl -X POST \
  -H "X-Appelium-Token: $APPELIUM_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "distributionGroupNames": ["Beta Testers"],
    "notifyTesters": true
  }' \
  https://api.appelium.com/v1/builds/$BUILD_ID/distribute

Attach release notes, filter builds and manage groups with the Builds and Distribution Groups APIs. Before you distribute, catch regressions with recorded UI tests. Once a release reaches the stores, follow its staged rollout with release health.

Frequently asked questions

Which builds can I distribute?

Upload an .ipa for iOS or an .apk for Android. Appelium reads the app identifier, version, build number, minimum OS version and SDK from the binary. iOS builds must be signed for installation outside the App Store, with a Development, Ad Hoc or In House profile that allows your testers’ devices.

Who can install a build?

Members of the distribution groups you distribute the build to. Groups are private by default: invited testers receive the Tester role, which can install distributed builds but has no Dashboard access. Enable public distribution for a group when anyone with its link should be able to install.

Do distributed builds expire?

iOS builds stop installing when their provisioning profile expires, so Appelium shows each build’s expiration date and marks expired builds in the list. Android builds do not expire.

How do I automate distribution, and which plans include it?

App distribution is included in every plan. Upload builds from any CI/CD pipeline with a single REST endpoint, attach release notes, then distribute to one or more groups and optionally notify testers by email. You can do the same manually from the Dashboard.

Put your next build in testers’ hands

Upload from CI, distribute to the right group and hear back sooner.

You are in a good company - Join over 150 apps!

Over 150 apps in Switzerland choose to use Appelium.

homegate
twint
timeplaces

👨‍💻 Latest content from our Engineering blog:

XPCService

  • Strongly typed bidirectional communication channel between UIApplication and XCUIApplication with powerful APIs and super fast performance.


    More about XPCService

Screen Flow Pattern in UI tests

  • Robust and scaleable pattern for structuring UI tests. Highly reusable screen verification code with human readable test case code. All flows and interactions statically typed 🙌.


    More about the Screen Flow Pattern

SnapshotQuery™

  • Learn about SnapshotQuery - our latest addition to AppeliumTests which radically improves the performance of your XCUITests while making them more stable and reliable at the same time.


    More about SnapshotQuery

Early access and news

Be the fist one to know about all the exciting engineering posts and product announcements.