Use case

iOS ad-hoc distribution, without the UDID spreadsheet

AirBuild distributes iOS ad-hoc builds via a shareable install link and automatically captures each tester's device UDID through a one-tap configuration profile, eliminating manual UDID collection before you can even ship a build.

Start Free

The problem with ad-hoc distribution

iOS ad-hoc provisioning requires every test device's UDID to be registered in your Apple Developer account before a build will install. Traditionally that means emailing testers, asking them to find their UDID (which isn't visible anywhere obvious on iOS), and manually adding each one to your provisioning profile — a process that breaks down fast past a handful of testers.

How it works

  1. 1

    Upload your ad-hoc-signed .ipa

    AirBuild parses Info.plist and the embedded provisioning profile on upload, detecting that the build is ad-hoc and needs device registration.

  2. 2

    Share the install link

    Testers open the link (or scan the QR code) on their iPhone/iPad. Before the app installs, they're prompted to install a .mobileconfig configuration profile.

  3. 3

    UDID captures automatically

    Installing the profile silently registers the device's UDID against your app in AirBuild — no copy-pasting, no spreadsheet.

  4. 4

    Export and re-provision

    View or export every captured UDID from the app's device registry, add them to your Apple provisioning profile, and re-upload a build signed for the expanded device list.

Related features

iOS OTA install (.plist/itms-services)

Live

Signed manifest generation and itms-services:// links for true over-the-air iOS installs.

Automatic UDID capture

Live

Testers install a .mobileconfig profile that registers their device UDID automatically — no manual collection.

Device registry & export

Live

View and export every captured device per app for your Apple provisioning workflow.

Automated ad-hoc re-signing

Roadmap

Automatically re-sign and redistribute a build the moment a new UDID is captured.

See all features →

Frequently asked questions

Do testers need to find their UDID manually?

No — installing the .mobileconfig profile that AirBuild generates registers the device's UDID automatically, with no manual lookup.

Does this work for builds already signed with a fixed provisioning profile?

UDID capture works for any ad-hoc build, but a device only gets access once its UDID is included in the provisioning profile used to sign the build — so you'll re-sign after collecting new UDIDs.

Is automatic re-signing after UDID capture available?

Automated ad-hoc re-signing is on our roadmap; today you export captured UDIDs and re-sign through your existing Apple Developer workflow.

Ship your next build in seconds

Free plan available. No credit card required to start.

Start Free