Registering tester UDIDs for iOS ad-hoc builds

This only applies to ad-hoc .ipa builds — the kind you export for internal testing outside the App Store. Apple restricts an ad-hoc provisioning profile to a fixed list of devices, identified by their UDID. A tester whose device isn’t on that list can open your install link, but the install itself will fail.

How App Dropper handles it

When a build is signed with a UDID-restricted provisioning profile, App Dropper reads the registered device list straight out of it at upload time — nothing for you to paste in manually. On the install page, a tester whose UDID isn’t already provisioned is walked through capturing it (opening the link on their device is enough), so you can see exactly which testers still need to be added to your Apple Developer account and re-signed into the build.

The usual workflow

1. Invite the tester and have them open the install link on their iPhone or iPad.
2. If their device isn’t in the provisioning profile yet, App Dropper flags it as missing rather than showing a confusing failed install.
3. Add the UDID to your ad-hoc provisioning profile in your Apple Developer account, re-export the .ipa, and upload the new build — same project, new version.
4. The tester reopens the same link and installs normally.

Skipping this entirely

UDID limits are an ad-hoc-specific constraint — they don’t apply to Android at all (see uploading a build), and don’t apply to iOS builds signed with an enterprise distribution certificate, which can install on any device without device-list limits.