Configure your application’s version and release stage to unlock powerful features.
Configuring your notifier with your application’s version and release stage will enable you to:
Where possible the notifier libraries will automatically detect the release stage but they each provide a way for it to be configured manually. In general the release stage will default to production if it’s not automatically or manually configured. See your platform’s docs for details.
You can set a primary release stage on a per-project basis by going to Project Settings > Release Stages. The primary release stage is used across the BugSnag dashboard to automatically display your most important data by default - for example in the stability center and releases dashboard.
Some notifier libraries will automatically detect the version of your application, including platforms where multiple version numbers are provided such as Android (versionName and versionCode) and iOS (Version and Build).
On platforms where the version cannot be automatically detected, the notifier libraries provide a way to set it. See your platform’s docs for details.
If you use GitHub, Bitbucket, or others, providing source control information such as your repo name, and commit hash has the following benefits:
To enrich releases with source control information, use one of our build tool integrations.
It is strongly recommended that the app version is configured in your notifier library. However, if doing so is not practical you can notify BugSnag that a new version has been released to a particular release stage by using the Build API with the autoAssignRelease release flag set. A version must be supplied but this can be anything unique such as a timestamp or commit hash. All subsequent errors reported for that release stage will be associated with that release.
This option is only applicable if a single version of your application is running at any one time (per release stage), for example a server side application. Note that errors reported around the time of a release may be associated with the wrong version depending on when BugSnag is notified of the build.