I'm using Dynatrace to monitor an android application (Android, XAMPP), I followed the instructions in the documentation, I did the instrumentation, generate the APK and deployed it in an emulator. The problem is in the last step of instrumentation when dynatrace is supposed to detect the visits, it continues to show the following message:
Anyone have an idea?
Solved! Go to Solution.
Hello @Babar Q.
Actually I'm using a Native application, I used the auto-instrumentation using wizard, it doesn't need any access to the source code:
Actually Dynatrace informes me that the instrumentation was done successfully, however it's not detecting visits, however when I simulate some actions I only get server side informations (purepaths ...) without getting UEM informations
Now this is very hard to predict whether Instrumentation was successful or not.
Did you enable the UEM?
Can you have visits from the Desktop Browser or Mobile browser?
As you said earlier that Web/App and Mobile are using the same path and agent then there should not be any issues in the agents logs because you already have visits from the Desktop Browsers.
I hope that you are using the XXXXX-final.apk distribution in the simulator.
Now this is really interesting that you have done almost everything correct even though problem persist.
What is your current version of AppMon?
I had faced almost the similar issue where all the beacons were skipping with the ADK 6.5.11 version and then I used ADK 6.3.22 version in our environment.
Dynatrace recently informed that they fixed that issue in the 6.5.16 version and many other mobile related.
Is it possible for you to update your environment or you the downgraded ADK like us?
Did you check the agent logs on the device? Maybe the agent is not able to successfully connect to your instrumented web server. There is a useful topic on the troubleshooting page from the 7.0 docu (should also work for 6.5): "How do I verify that the mobile agent is connected and can send data to the AppMon server?"
If the agent can send the data to the web server successfully, then you should check the visit dashlet. Sometimes the wizard is not able to detect the correct visit, but it is visible in the visit dashlet.