TestFlight on iPhone, the APK on Android, one QR code
Pro and Team
Many teams test iPhone builds in TestFlight and Android builds as an APK. That usually means two links in every message and two QR codes on every card, and testers who pick the wrong one.
Paste the public link of a TestFlight external group into a channel. The channel link then sends each phone to the right place, and the link and QR code never change.
Example
Beta channel
- iPhone and iPadTestFlight public link
- Android2.5 (121), APK
- Linkappforshare.io/c/...
Made for
- Teams whose iPhone testers already use TestFlight
- Apps tested at events, in shops or by clients with a printed QR code
- Anyone who wants iPhone testers without collecting UDIDs
What it ends
- Two links in every release message, one per platform
- Collecting UDIDs and rebuilding for each new iPhone tester
- iPhone testers opening the Android link and asking what to do
How it works
Step 1
Turn on the public link in TestFlight
In App Store Connect, open an external testing group and enable its public link. Apple gives you a link like testflight.apple.com/join/AbCd1234.
Step 2
Add it to a channel
On the project's Testing page press TestFlight next to the channel and paste the link. From CI: appforshare testflight <link> --channel beta --app <bundle id>.
Step 3
Share one link
iPhone and iPad visitors go to TestFlight, Android visitors get the newest APK of the channel, and a computer shows both with a QR code.
What changes for iPhone testers
TestFlight installs the build, so the tester needs no UDID and you never rebuild to add a device. Apple's rules still apply: a new external build goes through TestFlight beta review, and the public link has the tester limit you set in App Store Connect.
Remove the link from the channel and iPhones go back to the newest ad hoc build in it, if there is one.
Apps that check for updates
The channel's update check address for iOS includes the TestFlight link, so a test build can send people there instead of to an ad hoc install page.
Good to know
- AppForShare does not create the public link or submit builds for beta review: you turn the link on in App Store Connect.
- Install counts and tester status for the TestFlight side are in App Store Connect, not on the channel page.
Questions
- Do I need an App Store Connect key?
- No. You paste the public link. A key is only needed for features that change things in TestFlight, such as tester sync.
- Can I also offer the ad hoc build on iPhone?
- Not from the same channel. Use a second channel, for example QA, without a TestFlight link for registered devices.
- Which plan do I need?
- Pro or Team, the plans with channels.
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
- 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
- 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