sentry-java: Unable to deobfuscate stack trace even when mappings.txt is uploaded

Hello, I am using latest version 1.7.3 gradle plugin with gradle version 4.9. When I run assembleRelease task my build finishes successfully. However when my app crashes I still see obfuscated stack trace. How could I resolve this? Is there any way that I could view my uploaded mappings.txt file or at least verify that it’s really there? Logs:

> Task :app:persistSentryProguardUuidsForReleaseRelease
> compressing mappings
> uploading mappings
> Uploaded a total of 1 new mapping files
Newly uploaded debug symbols:
 4fcc9d17-473e-5bd5-b61b-f51608f43daf

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 41

Most upvoted comments

Awesome, thanks much for your help. I’ll try this out on an older version and then release this.

Thanks @Kazemir. I need to verify that works on an older version of Gradle/Android Plugin and then I’ll deploy that change.

@Kazemir You mean taking the generated sentry-debug-meta.properties file and manually dropping it into the intermediates dir for each build? I’m sure that works, but that seems like a short term workaround for something the Sentry plugin should do.

No, I mean that the path in this line: https://github.com/getsentry/sentry-java/blob/fdee75b2682c74935d947940006e4f3c21c2e91c/sentry-android-gradle-plugin/src/main/groovy/io/sentry/android/gradle/SentryPlugin.groovy#L136 should be replaced by return "${variant.mergeAssets.outputDir}/sentry-debug-meta.properties". But I’m not sure, that this solution suits for all Android Gradle Plugin versions.

Yeah, it takes a bit to sync and index in search. 😃