How to add a UDID to a provisioning profile
Updated
To add a UDID to a provisioning profile: register the device in developer.apple.com → Certificates, Identifiers & Profiles → Devices, then edit your ad-hoc profile, tick the new device and save. Download the updated profile (or let Xcode's automatic signing refresh it), re-archive and export the app, and share the new IPA.
1. Get the tester's UDID
Send them the free UDID finder — they open it on the iPhone or iPad and get the UDID in about 30 seconds, no computer needed. (What is a UDID?)
2. Register the device
- Sign in at developer.apple.com/account and open Certificates, Identifiers & Profiles.
- Choose Devices and click +.
- Pick the platform, enter a name (e.g. “Sam — iPhone 15”) and paste the UDID. To add many at once, use Register Multiple Devices with a tab-separated file.
- Click Continue and Register.
3. Update the provisioning profile
- Open Profiles and select your Ad Hoc profile for the app.
- Click Edit, tick the new device (or select all), and Save.
- Download the profile and double-click it — or, with automatic signing in Xcode, it updates the next time you archive.
4. Rebuild and share
An IPA carries the profile it was signed with, so the old file still won't install on the new device. Archive and export again with Release Testing, then upload the new IPA at ipalinked.com. You can confirm the device is included with the IPA analyzer.
The 100-device limit
Each membership year you can register up to 100 devices of each type (iPhone, iPad, Apple Watch, and so on). Disabling a device doesn't free its slot until your membership renews, when you can remove devices and start fresh. If you need more, look at enterprise distribution or TestFlight.
Frequently asked questions
Do I need to rebuild after adding a UDID?
Yes. The provisioning profile is embedded in the IPA, so you must re-export the app with the updated profile.
How many devices can I register?
Up to 100 per device type per membership year in a standard Apple Developer account.
Can Xcode add devices automatically?
Yes. With automatic signing, devices you connect and use as run destinations are registered and added to the development profile; ad-hoc profiles still need the device registered in your account.