UDID for app testing and provisioning
A tester's UDID is needed when an iPhone or iPad must be registered for a Development or Ad Hoc build. TestFlight normally does not require the tester to send a UDID because Apple distributes the beta through an invitation or public link.
By Alexander Tartmin · Published August 31, 2026 · Updated October 18, 2026
Which app-testing methods need a UDID?
The requirement depends on how the app is signed and distributed. Registered-device builds name the eligible hardware in provisioning, while TestFlight manages testers through App Store Connect instead.
| Testing method | Tester sends a UDID? | How access is granted |
|---|---|---|
| Development build | Yes, for a physical test device | The device is registered with the developer team and included by provisioning |
| Ad Hoc distribution | Yes | The registered device is selected in the Ad Hoc provisioning profile |
| TestFlight | Normally no | The tester accepts an email invitation or public link in TestFlight |
| Public App Store | No | The user installs the approved public release |
How a UDID enters the provisioning workflow
For manual registration, the developer adds a device name and UDID to their Apple Developer account. They then select the registered device when creating or updating a Development or Ad Hoc provisioning profile and export a build signed with that profile.
Adding a device after an app was exported does not change the old build. The developer needs to update the provisioning profile and distribute a build that contains the updated eligibility information.
- The tester copies the UDID from the exact iPhone or iPad that will run the app.
- The developer registers that device with their Apple Developer team.
- The developer includes the device in the appropriate provisioning profile.
- The developer exports and shares a build signed for the registered device.
What the tester should send
Send the UDID exactly as copied; do not substitute a serial number, IMEI, model name, phone number, or Apple Account email. Each physical device has its own identifier, so an iPad UDID cannot register an iPhone and a replacement phone needs its own registration.
A developer may also ask for the device model and iOS or iPadOS version when diagnosing compatibility. Share the UDID privately and only with the developer or organization responsible for the build.
Why a registered-device build may still fail
If installation reports that the device is not registered or eligible, first confirm that the copied UDID belongs to the device receiving the app. The developer should then verify that the device is active in the correct team and included in the provisioning profile used to sign the delivered build.
A build exported before the device was added can still carry the previous profile. The developer may need to regenerate or refresh provisioning, export again, and resend the build. Apple also requires Developer Mode when running exported iOS or iPadOS app packages outside TestFlight or the App Store.
Need the identifier?
Get your UDID in Safari
Open this page on the iPhone or iPad you want to identify and use the profile flow to copy the result.
Common questions
Is UDID needed for TestFlight?
Normally no. TestFlight testers accept an email invitation or public link and install through the TestFlight app. Development and Ad Hoc registered-device builds are the common cases that need a UDID.
Can I use the same UDID for my iPad and iPhone?
No. Each physical device has its own identifier. Run the flow on the exact device that needs to be registered.
Can a developer add my UDID after creating the app build?
They can register the device afterward, but the existing exported build does not update itself. The developer needs to update the provisioning profile and provide a build signed with the refreshed profile.
Why does the app say my device is not registered?
The UDID may be from a different device, the device may be inactive or registered under another team, or the delivered build may use a provisioning profile created before your device was added.
Sources
- Distributing your app to registered devices — Apple Developer
- Create an Ad Hoc provisioning profile — Apple Developer
- TestFlight overview — Apple Developer