From a tester's UDID to a registered device, without the Apple portal
Pro and Team
Ad hoc testing on iPhone has the same four chores every time: ask for the UDID, paste it into the Apple developer portal, remake the provisioning profile, tell the tester when a new build is ready. AppForShare turns that into one link and one button.
You build and sign the app yourself, on your Mac or on GitHub Actions. When a new iPhone joins later, you can build again or re-sign the build you already uploaded with the new profile (Pro and Team).
Example
Devices on Apple
- iPhone37 used, 63 left
- iPad4 used, 96 left
- Waiting to register3 devices
- Ad hoc profileMisses 3 enabled devices
Made for
- Developers who test on real iPhones outside TestFlight, for clients or before beta review
- Agencies whose clients cannot find a UDID on their own
- Teams that hit "this device is not in the profile" more than once a month
What it ends
- Explaining to a client how to find a UDID over email
- Copying 40 character strings into the Apple portal one at a time
- Forgetting to regenerate the profile, then a build that will not install
- Not knowing how many of Apple's device slots are left this year
How it works
Step 1
Send the onboarding link
Each iOS project has its own link. The tester opens it on the iPhone, enters an email and installs a small profile that sends us the UDID. No account needed.
Step 2
Register on Apple
The device appears in your workspace and you get an email. Register up to 20 devices at a time on your Apple account with one click; ones already there are skipped.
Step 3
Add them to the profile
Your ad hoc and development profiles show how many enabled devices they miss. "Add new devices" remakes the profile with all of them, ready to download.
Step 4
Build again or re-sign, then share
Build again with the new profile, or re-sign the newest build with it from the build page. When a build that includes the tester's device is ready, the tester gets one email with the install link.
Apple's 100 device limit, in plain view
Apple allows 100 devices per device type (iPhone, iPad and so on) in each membership year, and a disabled device keeps its slot until renewal. We show used and remaining slots per type and stop before the limit instead of letting Apple refuse the request halfway.
Profiles you can download
Apple has no way to edit a profile, so "Add new devices" makes a new one with the same name, app ID and certificates and removes the old one. Download the .mobileprovision, or let a GitHub Actions build pick it up. Profiles that Xcode manages on its own are left to Xcode.
Bring the devices you already have
The Devices page imports a list of UDIDs on every plan with an account: the file Firebase App Distribution makes with Export Apple UDIDs, the file Apple's Register Multiple Devices page takes, one UDID per line with an optional name, or the JSON that eas device:list --json prints for devices registered with Expo. Up to 1,000 devices per import; devices you already have keep their data, and every line that is not an iPhone or iPad UDID is listed with the reason.
The other way works too: download your devices in Apple's format for the Apple portal or for fastlane register_devices. From CI: appforshare devices import and appforshare devices export.
Testers see if their iPhone is in the build
A tester who checked the iPhone once with the UDID finder can tap Remember this device. Every iOS install page then says whether the build includes that iPhone before Install, and when the onboarding link is on, the tester sends the iPhone to you from the page. It lands in your devices like an onboarding request. This check works on every plan.
Or let it run on its own (Team)
With Hands free on, a device that arrives through the onboarding link is registered on Apple a few minutes later, the ad hoc profile is made again when your build reads one, and the project's GitHub iOS build starts. The tester gets the install email when that build is uploaded. An Admin turns it on per project.
Good to know
- Registration is never automatic unless an Admin turns on Hands free for that project (Team). Otherwise an Admin of your workspace presses the button.
- After adding devices, a build needs the new profile: build again, or re-sign an uploaded iOS build with it. Re-signing needs your signing certificate added once in Settings.
- Apple's slots cannot be freed before your membership renews, by us or anyone.
- Needs an App Store Connect connection with a key that can manage devices.
Questions
- Does the tester need an Apple or AppForShare account?
- No. They open the link on the iPhone, enter an email (and a name if they like) and install the profile Apple uses to share a UDID.
- Can I still find a UDID without a paid plan?
- Yes. The UDID finder at /udid is free and saves devices to your account, and any account can import a UDID list on the Devices page. Registration on Apple and the onboarding link are on Pro and Team.
- I am moving from Firebase App Distribution. Do my testers send their UDIDs again?
- No. In the Firebase console open App Distribution, the Testers & Groups tab, select All testers and press Export Apple UDIDs. Import that file on the Devices page and the devices are in your list.
- What happens after I register a device?
- Remake the ad hoc profile with "Add new devices", then build again with it, or re-sign the newest build with it from the build page (no rebuild). The tester gets one email with the install link once a build includes their device. With Hands free on, those steps run for you.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications