Releases & versions

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:

  • filter your dashboard by release and identify which release errors were introduced in.
  • see release annotations on the timeline to correlate new versions with changes in error rates.
  • enable the releases dashboard.

Configuring the release stage

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.

Configuring your app version

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.

Source control information

If you use GitHub, Bitbucket, or others, providing source control information such as your repo name, and commit hash has the following benefits:

  • The releases dashboard and release annotations on the timeline will link to the version of your code in that release, and the diff from the previous release.
  • Stack traces will link directly to view the line of code (on some platforms).

To enrich releases with source control information, use one of our build tool integrations.


What should I do if it’s not possible for me to set the version in my notifier library?

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.