Closed MohammadRezaei92 closed 3 years ago
Hello @MohammadRezaei92! Thanks for opening the issue. Do you see any errors/warnings related to this plugin when you run mapping upload task?
Hello @MohammadRezaei92! Thanks for opening the issue. Do you see any errors/warnings related to this plugin when you run mapping upload task?
As far as I see there is no warning or error.
@MohammadRezaei92 Can you please run this task with info
log level enabled? This should give more information. You can check how to do it here https://docs.gradle.org/current/userguide/logging.html
@MohammadRezaei92 Can you please run this task with
info
log level enabled? This should give more information. You can check how to do it here https://docs.gradle.org/current/userguide/logging.html
@MohammadRezaei92 Thanks for the info! Can you please confirm that you see non-obfuscated stacktrace in RUM (because we don't do de-obfuscation in Logs yet)? Also can you please check that service name which is used during Datadog.initialize()
call is the same as in the plugin configuration?
@MohammadRezaei92 Thanks for the info! Can you please confirm that you see non-obfuscated stacktrace in RUM (because we don't do de-obfuscation in Logs yet)? Also can you please check that service name which is used during
Datadog.initialize()
call is the same as in the plugin configuration?
I see stack-trace in RUM like this
@MohammadRezaei92 If you are using custom service name please check it matches the values used in Datadog.initialize
, also please check that stacktrace entry is generated at the app version which had mapping file uploaded (we don't apply mapping file for the particular version to another versions). If everything looks good, please open support ticket (https://docs.datadoghq.com/help/) with the details of your App ID/Org ID, so that we are able to continue looking on the issue more precisely.
@MohammadRezaei92 If you are using custom service name please check it matches the values used in
Datadog.initialize
, also please check that stacktrace entry is generated at the app version which had mapping file uploaded (we don't apply mapping file for the particular version to another versions). If everything looks good, please open support ticket (https://docs.datadoghq.com/help/) with the details of your App ID/Org ID, so that we are able to continue looking on the issue more precisely.
We don't use a custom service name and the version number is OK.
Hello @MohammadRezaei92. The issue is solved now and to summarize, the reason was:
variant
should be specified when Datadog SDK is initialized. This API is available with dd-sdk-android >= 1.8.0
Thanks for taking the time for reporting an issue!
Describe what happened I added gradle plugin and did the configuration. Gradle task for upload mapping file run successfully but still my stack-traces are obfuscated.
Steps to reproduce the issue:
Describe what you expected: Seeing stack-trace de-obfuscated.
Additional context