Testers stop testing last week's build
Pro and Team
The link and the email reach testers once. After that, many keep the build they have and report bugs you fixed days ago. With the update check, the test build itself notices when its channel has a newer build and offers the install link.
It is one public JSON address per channel and a few lines in your app. Nothing to add to your build system, no SDK to keep up to date.
Example
Beta channel, Android
- Installed on the phoneBuild 116
- Newest in the channelBuild 118
- Your app showsUpdate available
Made for
- Teams that ship a test build every day or two
- Agencies whose client testers forget to check their email
- Apps tested in the field, where the QR code was scanned once
What it ends
- Bug reports against builds that are already fixed
- Asking testers which version they are on
- Sending the same link again after every build
How it works
Step 1
Put builds into a channel
For example Beta, from the dashboard or CI. The channel always knows its newest build per platform.
Step 2
Add the snippet
Copy the Swift, Kotlin, Flutter or React Native code from the docs, with your channel address from Projects, Testing, Update check.
Step 3
Testers get the prompt
When the channel has a higher build number, your app shows your own message and opens the install page.
What the app reads
The channel answers with the version, the build number (iOS CFBundleVersion, Android versionCode), release notes, the install link and when the build went in. Put an older build back into the channel and apps see that one, so a rollback reaches testers too. Release notes stay hidden for password protected builds.
When a build is retired
If you retire a broken build, the channel skips it. Send the app's own build number with ?build= and the answer also says whether that build is retired, with your note, plus minBuild: one above the highest retired build number of the app and platform. Your test build can then ask the tester to update before going on.
Good to know
- Keep the check out of store builds entirely: compile it only into a beta flavor or configuration. App Store guideline 2.5.2 and Google Play's policy on self updating apps do not allow it there, even as unused code.
- On iPhone the new build must include the tester's device, as with any ad hoc build.
- The app shows the prompt and opens the link; installing stays a tap by the tester.
Questions
- Is there an SDK?
- No. Your app makes one HTTPS request and compares two numbers. The docs have code for Swift, Kotlin, Flutter and React Native.
- 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
- TestFlight and APK in one link
- Install page in 13 languages
- .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