Closed mrjameshamilton closed 1 year ago
Hi @mrjameshamilton, thanks for reporting. This is something we are aware of and is on our backlog to fix.
in the meantime you can still manually upload your dexguard mappings using our CLI https://docs.bugsnag.com/build-integrations/bugsnag-cli/upload-android-proguard
Hi @johnkiely1 ! We've added the version
field back into the DexGuard Gradle plugin which should resolve the compatibility and no changes should be required in bugsnag. It will be in DexGuard 9.4.15.
Hi @mrjameshamilton, That's great, thanks for informing us! Are you happy for us to close out this ticket, or do you have any further questions?
Thanks, the issue can be closed!
Describe the bug
The
version
field has been removed from DexGuard Gradle Plugin which means that the version check here throws aMissingPropertyException
and then Bugsnag thinks that DexGuard is not being used.The manifest fallback is still there when using the
path
, so the plugin could check if the property exists first.But this doesn't work if the
path
option is not used i.e. DexGuard is retrieved from a Maven repository.Additionally, detecting earlier versions of DexGuard relied on the exception, so this might causes issues for older versions.
Steps to reproduce