Allow overriding the versionCode via Configuration #610
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Allows overriding the
versionCode
either through a manifest meta-data element or programmatically on theConfiguration
object. This facilitates grouping for custom versioning schemes. By default, theversionCode
still uses theandroid:versionCode
manifest value once aClient
has been instantiated.Changeset
Added integer
versionCode
field toConfiguration
which can also be read via the AndroidManifestmeta-data
elementcom.bugsnag.android.VERSION_CODE
. By default if this value is not configured, theClient
will set theversionCode
to the value supplied inandroid:versionCode
of the AndroidManifest.Tests
Ran the example app and confirmed that for a handled, unhandled, and NDK error, the versionCode reported in the dashboard differs for:
android:versionCode
value set in the manifestcom.bugsnag.android.VERSION_CODE
value set in the manifestconfig.versionCode
Updated existing integration tests to verify that the value is loaded from the manifest and can be overridden.