Our App team has reported that with Android Agent of v7.1.4 was changing the url paths in the app and when they used latest 7.1.9 agent they are not seeing that issue. Is it a known issue fixed in latest version? Has anyone else faced similar issue?
Solved! Go to Solution.
Do you use auto-instrumentation? Because there was a critical problem regarding string identifiers for multidex applications in version 7.1.4. This problem could explain the scenario you are facing with version 7.1.4.
The problem was fixed in version 7.1.6:
ONE-15836 - Android Auto-Instrumentation: Certain multidex
applications, that have a high string identifier count and a high number
of referenced methods in one of their dex files, suffer from string
Then it could be that your app is affected by the mentioned problem. Here is a short (very technical) description: The 3rd party library, that is used by the auto-instrumentor to modify the bytecode, is not able to dynamically adjust const-string instructions, when the auto-instrumentor adds new string identifiers to the DEX file. In version 7.1.5 and 7.1.6 we changed the multidex preprocess step and how it converts non-jumbo const-string instructions to jumbo const-string instructions to avoid the problem.
The Android agent does not modify url paths. It only attaches the "x-dynatrace" header on your native web requests.