Discussion Feed

Nick.Silin · ‎06-11-2021

Just checked again.. Indeed, there are some cases when it is working. # For instance, when I run build in terminal: ``` ./gradlew --stop // to make sure no other Gradle daemons which could affect the build ./gradlew clean ./gradlew assembleDebug ``` It builds fine by some reason. # When I try to build it from Android Studio (4.2.1) by clicking Build action ("Make Project"), it can build first time, but when I try to Run project on device ("Run app" action) after this, it fails and then failing all the time for both Build and Run actions. So I am just wondering if this "buildID" somehow cached inside plugin and this cache becoming broken between builds to different Gradle daemons.

Nick.Silin · ‎06-08-2021

Hi Previously, I had a request (Zendesk ticket #215430) for investigating issue with Proguard files not automatically uploaded, which was supposed to be fixed in 21.5.0. But after updating to 21.5.0 new issue appeared: "Cannot get property 'buildID' on extra properties extension as it does not exist" It looks like someone leaked some private API to public AppDynamics Gradle plugin API, because it looks like the plugin always assumes "buildID" value provided via extra property. It can be easily workarounded by providing some random value in project "ext", e.g. ext.buildID = "AppDynamics workaround value" After this project compiles fine. But I have no idea how it will affect rest of the functionality. As it is nowhere mentioned in official docs, still need some official guidance how to fix this issue. I also have samle project where it is reproducible: https://github.com/silin/appdynamics-mapping-upload-issues It is based on standard Android project with basic AppDynamics plugin setup

Nick.Silin · ‎05-14-2020

Looks like the issue is fixed in `20.5.0` - after updating to this version for us the issue is gone

Nick.Silin · ‎05-12-2020

Probably also related or same issues as here: https://community.appdynamics.com/t5/End-User-Monitoring-EUM/AppDynamic-EUM-setup-for-Android-Cordova-project/m-p/38864/highlight/false#M1225

Nick.Silin · ‎05-12-2020

Have the same version on our native Android project (not Cordova) too Android plugin: 3.6.3 AppDynamics: 5.2.1552 and 20.4.0 The same project setup works if Android plugin downgraded to 3.5.X version The same project setup works with Android plugin 3.6.X and removed AppDynamics Do you guys have any timelines for fixing the issue or reference to some open bug to track its progress? It is a bit disappointing that this plugin basically blocks upgrading projects using AppDynamics to use latest Android tools. In our organization we have relatively big Android team and no one able to use latest tools already for 2 months because of the issue without removing AppDynamics plugin. I just hope you understand that the issue is critical and probably such issues should be resolved much faster, because using outdated tools for few months (Android plugin in this case) affects teams productivity and have cost, so at some point teams will have to switch to some other tool

Date Registered	‎12-23-2019 07:31 AM
Date Last Visited	‎06-17-2021 03:57 AM
Total Messages Posted	5
Total Kudos Received	3

Discussion Feed

Re: Android plugin 21.5.0 issue with missing "buil...

Android plugin 21.5.0 issue with missing "buildID"

Re: AppDynamic EUM setup for Android Cordova proje...

Re: AppDynamics Android Gradle Plugin 20.4.0 issue...

Re: AppDynamic EUM setup for Android Cordova proje...