topic Re: Auto-instrumenting an Android app for UEM, Obsfucated apk. in Real User Monitoring

Auto-instrumenting an Android app for UEM, obfuscated apk

alejandro_herna — Mon, 19 Jun 2023 11:27:43 GMT

We are trying to use auto-instrumentation to instrument the Android UEM, they use obfuscation when creating the apk file with proguard:
-proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
Would this cause any problem with the auto-instrumentation, would it work?

Re: Auto-instrumenting an Android app for UEM, Obsfucated apk.

Thomas_Wirth1 — Tue, 24 Apr 2018 05:50:59 GMT

Hey Alejandro,

Yes, you have to exclude some parts from obfuscation and optimization. Regarding your other question, you have to exclude the OkHttp3 library from obfuscating. You find the details in the documentation.

When you enrich your mobile user experience data via the OneAgent SDK for Mobile, then you also have to exclude the OneAgent library from obfuscating. This step is not needed, when you use the latest agent (version 7.1).

Re: Auto-instrumenting an Android app for UEM, Obsfucated apk.

alejandro_herna — Thu, 26 Apr 2018 14:53:57 GMT

Than you @Thomas W.

Re: Auto-instrumenting an Android app for UEM, Obsfucated apk.

Patrick_H — Wed, 04 Jan 2023 09:31:29 GMT

update: recent plugin version (8+) performs the instrumentation before obfuscation is done, thus the obfuscation rules no longer need to be adjusted. Details can be found here: https://www.dynatrace.com/support/help/shortlink/dynatrace-android-gradle-plugin-overview#instrumentation-specific-capabilities