Sentry-java: Thread info is not present with 3.1.0 (Android-ANR)

[ItsReddi]

_Platform:_

• [x] Android

_IDE:_

• [x] Android Studio

_Build system:_

• [x] Gradle

_Sentry Android Gradle Plugin:_

• [x] Yes
• [ ] No

_Proguard/R8:_

• [x] Enabled
• [ ] Disabled

The version of the SDK:
3.1.0

---

I have the following issue:

After upgrading from 2.3.2 to 3.1.0 ANR reports do not include any thread informations.

Steps to reproduce:

• 
  
  1. use 2.3.2
  
  
• 
  
  1. example ANR
  
  

if (true) {
                    int a = 0;
                    while (true) {
                        a++;
                    }
                }

Result:

• 
  
  1. switch to 3.1.0
     
     Result:
     
     
  
  

[marandaneto]

thanks for raising this, would you mind to try again but enabling SentryOptions.attachThreads? thanks

[marandaneto]

this should have done the job: https://github.com/getsentry/sentry-java/blob/5ebd49cbfd17eb66175e9247db6d27e4df84a56b/sentry-android-core/src/main/java/io/sentry/android/core/ApplicationNotResponding.java#L24
I mean it does, but it doesn't look like having the whole stack traces or it's reporting the capturing thread but not the UI one.

[ItsReddi]

SentryOptions.attachThreads does not seem to make a difference.
Still no threads attached on ANR.
but im unsure it is correct how it is enabled?

[marandaneto]

@ItsReddi this config is not available on the manifest config.

you need to: https://docs.sentry.io/platforms/android/usage/advanced-usage/#manual-instrumentation
and do options.setAttachThreads(true)

[ItsReddi]

I can confirm it works with setAttachThreads(true)

[marandaneto]

thanks, @ItsReddi we'll be looking into it, this flag should not have interfered in the ANR threads/stack traces if I am guessing it right.
you could use the setAttachThreads workaround for now :)

[ItsReddi]

Allright, but it would now add the thread info to any Event, also Exceptions, custom errors if i understand the SentryOptions Docs correct?

Any way to enable that only for ANR?

[marandaneto]

true, this was enabled by default on sentry-android v2 anyway, so it's not really a problem to send all the threads info, the thing is, most of them are not useful for you to debug the issue.

unfortunately, it's not possible to enable only for ANR, this would be the bugfix, what you can do is, to use the beforeSend callback and filter them out based on the exception type (if not ANR).

[marandaneto]

just tested it out, https://github.com/getsentry/sentry-java/releases/tag/4.0.0-alpha.2 should give you stack traces of the main thread ootb, no need for setAttachThreads unless you want to see stack traces of all the running threads.

Thanks for reporting :)