Cisco AppDynamics Community

Pablo.Coberly · 03-09-2021

Android agent plugin version: com.appdynamics:appdynamics-gradle-plugin:20.10.0 Using the Android Gradle plugin and calling an assembly task for a particular Android product flavour & build type puts the mapping files in an output folder that the App...

Pablo.Coberly · 04-06-2021

Appdynamics says "Developers confirmed that this issue will be fixed for the next Agent update, which should come out next month."Boggles my mind that I have to give these updates in this forum and not Appdynamics people themselves.

Pablo.Coberly · 03-12-2021

I raised a support ticket with AppDynamics support and they were able to reproduce the issue. The dev team are working on a resolution.

Pablo.Coberly · 03-10-2021

FYI, I've updated the Gradle plugin and run time versions to the latest versions: // App dynamics Pluginclasspath "com.appdynamics:appdynamics-gradle-plugin:21.2.1"implementation 'com.appdynamics:appdynamics-runtime:21.2.1' And the same thing happens...

Pablo.Coberly · 03-10-2021

I've tried specifying the mapping file location in the proguard-rules.pro: -printmapping build/outputs/mapping/test/mapping.txtBut again, it seems the task appDynamicsUploadProguardMappingTestProd is looking for the mapping files before they are ther...

Cisco AppDynamics Community

User Statistics

User Activity

Android Proguard mapping files are not found when using product flavour & build type combinations

Re: Android Proguard mapping files are not found when using product flavour & build type combinations

Re: Android Proguard mapping files are not found when using product flavour & build type combinations

Re: Android Proguard mapping files are not found when using product flavour & build type combinations

Re: Android Proguard mapping files are not found when using product flavour & build type combinations