Tester distribution

Upload a build from the console (Authentication › Mobile › Tester builds), the CLI or a GitHub Action. Sovaria reads the build (package or bundle id, version, build number, minimum OS and, for iOS, the provisioning profile), shares it with tester groups and emails each tester their own install link. Builds sit in a private bucket of your project that no storage API can reach; downloads are signed links that expire after 10 minutes.

sov distribute upload app-release.apk --groups qa,beta --notes "Fixes checkout"
sov distribute testers add ann@example.com bob@example.com --groups qa
sov distribute releases

#Testers and links

• A tester opens the link on their phone: the page lists the builds their groups can see, with release notes. No account is needed; the link is the credential.
• Links are signed for each tester and expire with the plan's install window. Removing a tester, or sending them a new link, stops their old links at once.
• Android: testers install the APK (allow installs from the browser). An AAB can be stored but phones can't install it; upload an APK for testers.
• iOS: the build must be ad-hoc (the tester's device in the provisioning profile) or enterprise signed; the page installs it over the air. App Store builds go through TestFlight.
• Builds can carry the environment they talk to and the commit they came from (--env, --git-ref), so a preview build points at its preview environment.

#Plans and limits

Build files count against your storage, invites against your emails, and downloads against egress. Older builds beyond the plan's count are deleted, and builds stop installing after the install window. Under HIPAA mode tester distribution is off by default.