On integrating bugsnag-android-gradle-plugin to upload mappings at the build time, our release builds fail on having invalid api key. Normally the valid api key is fed to a placeholder so it can be accessible only in specific setups but invalid in others.
Design
Ths proposed change should prevent failing release builds in setups where the api key shouldn't be accessible. It increases the flexibility of the plugin usage regardless having a valid/invalid api-key while at the same time retain logging errors if any.
Changeset
Similar to the case now in bugsnag-android, where an invalid api-key, example, prevent sending events to the dashboard without failing builds. The proposed change stops concerned exceptions
Testing
Automated tests should pass normally. Below screenshots might give more visibility
Goal
On integrating
bugsnag-android-gradle-plugin
to upload mappings at the build time, our release builds fail on having invalid api key. Normally the valid api key is fed to a placeholder so it can be accessible only in specific setups but invalid in others.Design
Ths proposed change should prevent failing release builds in setups where the api key shouldn't be accessible. It increases the flexibility of the plugin usage regardless having a valid/invalid api-key while at the same time retain logging errors if any.
Changeset
Similar to the case now in
bugsnag-android
, where an invalid api-key, example, prevent sending events to the dashboard without failing builds. The proposed change stops concerned exceptionsTesting
Automated tests should pass normally. Below screenshots might give more visibility
Before change
After change