HI @Ryan.Paredez ,
Thanks for your reply, for the account and license key I did not use the trail account, I was using our customer's license Key which encountered the error.
The current result is once we enable the code obfuscation, the AppDynamic returns a Bad credential error
After that we did some testing:
for both testing versions, we added the below code into progurad-rule.pro
-keep class com.appdynamics.eumagent.runtime.DontObfuscate
-keep @com.appdynamics.eumagent.runtime.DontObfuscate class * { *; }
AppDynamic version 22.2.2
appdynamic_gradle_plugin version: 22.2.2
it failed in
> Task :app:appDynamicsProcessProguardMappingDevRelease FAILED Execution failed for task ':app:appDynamicsProcessProguardMappingDevRelease'. > Bad Credentials, please verify the account and licenseKey in your build.gradle file.
and the logcat from Android studio shows
Error clearing beacons from database
Error reading beacons from database
I think it should be the code obfuscation still makes the inter error for the AppDynamic.
2. appDynamic version: 20.11.1
appdynamic_gradle_plugin version: 20.11.1
it failed in
':app:appDynamicsUploadProguardMappingRelease' (type 'UploadProguardMappingFileTask'). - In plugin 'adeum' type 'com.appdynamics.android.gradle.UploadProguardMappingFileTask' property 'applicationName' is missing an input or output annotation.
Try: > Run with --info or --debug option to get more log output. > Run with --scan to get full insights.
Exception is: org.gradle.internal.execution.WorkValidationException: Some problems were found with the configuration of task ':app:appDynamicsUploadProguardMappingRelease' (type 'UploadProguardMappingFileTask'). - In plugin 'adeum' type 'com.appdynamics.android.gradle.UploadProguardMappingFileTask' property 'applicationName' is missing an input or output annotation. Reason: A property without annotation isn't considered during up-to-date checking. Possible solutions: 1. Add an input or output annotation. 2. Mark it as @Internal.
... View more
