Install Groups
Control which iOS builds can see updates for each other using install groups.
This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony.
Install groups let you tag builds with one or more group names to control update visibility between builds. See the product documentation for a full explanation of how install groups work.
Pass --install-group one or more times:
sentry-cli build upload app.xcarchive \
--org your-org \
--project your-project \
--build-configuration Release \
--install-group alpha \
--install-group staging
Pass the install_groups parameter:
Fastfilesentry_upload_build(
org_slug: 'your-org',
project_slug: 'your-project',
xcarchive_path: 'path/to/YourApp.xcarchive',
build_configuration: 'Release',
install_groups: ['alpha', 'staging']
)
When the Auto-Update SDK checks for updates, the server returns the single latest build (highest semver version, with build number as tiebreaker) whose install groups overlap with the filter:
- If the SDK sends groups explicitly, the server uses those to filter.
- If the SDK doesn't send groups, the server looks up the uploaded build using the device's Mach-O UUID of the app binary and uses that build's upload groups for filtering.
Because the Mach-O UUID is unique per binary, the server can reliably identify the correct build. This means tagging builds with install groups at upload time is sufficient on iOS — the server inherits the correct groups automatically when checking for updates.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").