Showing results for 
Show  only  | Search instead for 
Did you mean: 
AppDynamics Team (Retired)


When the mapping file is uploaded to get de-obfuscated stack trace, we do not see the de-obfuscated stack, but following message is seen:

We didn't find a mapping file that exactly matches your application with build id '<build_id_1>'. 
Deobfuscation was done using a mapping file that was built with an older version of appdynamics plugin.


For the de-obfuscated stack trace, following is seen:

De-obfuscated stack trace: 
java.lang.IllegalStateException : Can not perform this action after onSaveInstanceState 




This issue occurs whem the mapping.txt that was uploaded is for build '<build_id_2>', while that crash is for build '<build_id_1>'.  So the exact mapping file is not uploaded at the time the crash appeared.

When the EUM Processor cannot find the exact proguard file it needs, it looks for similar ones.  In this case, it found a different one, but it won't help in this scenario.



To resolve this issue, we recommend to turn on automatic proguard upload in the script that builds the app.  That way we can be sure that every proguard mapping file is uploaded.


More Information:


If you update your application, you need to upload the new version of the mapping file. To associate the mapping file with the correct version of the application, you need to provide:

  • the package name of the Android package for the application
  • the version code for that application from the AndroidManifest.xml file

Version history
Last update:
‎12-21-2018 04:07 PM
Updated by:
June 26 Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.

Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!

Read the blog here