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 API returns the single latest build (highest semver version, with build number as tiebreaker) whose install groups overlap with the filter:
- If the SDK provides groups explicitly, the API uses those to filter.
- If the SDK doesn't provide groups, the API looks up the uploaded build using the UUID of the app binary and uses that build's upload groups for filtering.
UUID matching is not guaranteed to identify the build you uploaded. The UUID is only unique to an app's main binary, so an upload that only changes other files such as images won't be differentiated.
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").