cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Android ProGuard cause Bad Credentials issue,, and the solution not working

Tianlin.Feng
Wanderer

Hi AppDynamic team,

I have faced an issue when enable the code obfuscation in ProGuard after upgrade appDynamic version from 20.11.1 to 22.2.2 .

also add below code into progurad-rule.pro

-keep class com.appdynamics.eumagent.runtime.DontObfuscate
-keep @com.appdynamics.eumagent.runtime.DontObfuscate class * { *; }

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.

But I could confirm that the LicenseKey was correct and did not changed,(it works fine in version 20.1.1)

 

Could you please help me out for this?

Thanks

 

5 REPLIES 5

Ryan.Paredez
Community Manager

Hi @Tianlin.Feng,

Did you get assigned an Account/Sales Rep through any of your trial sign up emails?


Thanks,

Ryan, Cisco AppDynamics Community Manager




Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.



Check out Observabiity in Action

new deep dive videos weekly in the Knowledge Base.

Ryan.Paredez
Community Manager

Hi @Tianlin.Feng,

Following up from my above question


Thanks,

Ryan, Cisco AppDynamics Community Manager




Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.



Check out Observabiity in Action

new deep dive videos weekly in the Knowledge Base.

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.

 

Emily.Wang
Moderator
Moderator

Hi Tianlin,

Which customer account are you with?  Have you tried to get some help through AppD Support for this?  That would be the fastest way to make progress on this issue.    

 

Emily Wang

End User Monitoring Product Lead

 

Hi Emily,

Sorry, we could not post from our customer account since the security policy, and could I ask where I should get the support from appD Support?