A new iPhone tester gets the build without you in between
Team, turned on by an Admin per project
Adding one iPhone tester to an ad hoc build takes four people steps: register the UDID, remake the profile, build again, tell the tester. Usually the tester waits a day because the developer was busy.
Hands free does those steps for one project. The tester sends the device through the onboarding link as before. A few minutes later AppForShare registers it on your Apple account with your App Store Connect key, makes the ad hoc profile again when your build reads one, and starts the project's iOS build on your GitHub Actions. Without a GitHub build, it re-signs the newest iOS build of the project with the new profile instead. When the new build is ready, the tester gets the email with the install link.
Example
Hands free, Shop app (iOS)
- Registered on Apple3 iPhones
- Ad hoc profileMade again with every device
- GitHub iOS buildStarted
- TestersEmailed when the build is uploaded
Made for
- Agencies whose client testers join in the middle of a test round
- Teams that test ad hoc builds on real iPhones every week
- Developers who already build iOS on GitHub Actions with AppForShare
What it ends
- A tester who sent the UDID on Monday and installs on Wednesday
- Registering one device in the Apple portal, then forgetting the profile
- Starting a build just to add a single iPhone
How it works
Step 1
Get the pieces ready
The project needs its device onboarding link on, an uploaded iOS build so AppForShare knows the app, and an App Store Connect connection. A GitHub iOS build for the app lets the last step run too.
Step 2
An Admin turns it on
On the project's Testing tab, under the device onboarding card, an Admin switches on Hands free. Devices that arrived earlier are picked up by the first run.
Step 3
Testers send their iPhone
They open the onboarding link, enter an email and install the small profile, as before. AppForShare waits a few minutes so several devices go in one run.
Step 4
The run does the rest
Register on Apple, remake the ad hoc profile if needed, then start the GitHub iOS build or re-sign the newest build with the new profile. You get one email per run with what was done; each tester gets the install link when the new build is ready.
Which profile is made again
With manual signing in your GitHub iOS build, or with no GitHub build at all, AppForShare remakes the active ad hoc profile of the app with every registered device. With Xcode automatic signing, Xcode adds the new devices to its own profile during the build, so AppForShare leaves that profile alone.
Without a GitHub iOS build, the run re-signs the newest iOS build of the project with the remade profile, as a new build, when the workspace has added its signing certificate in Settings. The source build and its link stay as they were. Without the certificate the run stops after the profile: you build and upload, and the testers are emailed then.
Safeguards
Apple allows 100 devices per device type in each membership year. That limit is checked before Apple is asked, and a run registers at most 10 devices, with at most 20 a day on the same Apple account; the rest wait for the next run. Every call to Apple is in the connection's activity log, and every run is a line in the workspace activity feed.
Only an Admin can turn Hands free on, because it uses your Apple account. Turning it off stops new runs at once.
Good to know
- Only devices sent through the project's onboarding link are registered. Devices you import or add by hand still need the Register button.
- The new build is made on your own GitHub Actions minutes, by you, or by re-signing your newest uploaded build. Re-signing needs the workspace's signing certificate and an ad hoc profile; it never changes the bundle ID, version or build number.
- Apple's device slots cannot be freed before your membership renews. A registered device keeps its slot.
- Needs an App Store Connect key that can manage devices and profiles.
Questions
- Is anything registered without my say?
- Only after an Admin turns Hands free on for that project. After each run the account owner gets one email with what was registered, which profile was made and whether the build started, or what needs a person. Without Hands free, registration waits for the button.
- What does Firebase App Distribution do here?
- Firebase collects the UDID when the tester signs up and emails it to you. Registering it on Apple, the new profile and the new build stay with you.
- Do I need GitHub Actions?
- No. Without a GitHub iOS build, Hands free re-signs the newest build of the project with the new profile, once an Admin has added the signing certificate in Settings.
- Which plan do I need?
- Team. The onboarding link, one click registration and re-signing by hand are on Pro and Team; Hands free, with its automatic re-signing, is on Team.
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
- iOS device registration
- 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