-
-
Notifications
You must be signed in to change notification settings - Fork 444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sentry Performance crash: Caused by java.lang.NullPointerException: Attempt to invoke virtual method 'int java.util.ArrayList.size()' on a null object reference #1798
Comments
@dmytroKarataiev thanks for reporting. our SDK does call |
Sentry uses AndroidX.Core 1.3.2 min. How to do it: https://docs.sentry.io/platforms/android/performance/instrumentation/automatic-instrumentation/#androidx-support |
1.6.0.
And confirmed that it was forced with gradle dependencies scan, but it didn't help either. The issue is still easily reproducible on any Android 9 device (including an emulator). |
@dmytroKarataiev thanks for the reply. I've tried to reproduce using Android 9 emulator and androidx.core 1.6.0, with no success, would you mind setting up a minimal reproducible example on GH or giving me exact steps? maybe you have a custom setup in your Activity that triggers this error? |
i have the same problem. |
I think there are two solutions:
|
thanks @HenryHaoson I cannot add back to good finding with the https://android.googlesource.com/platform/frameworks/base/+/140ff5ea8e2d99edc3fbe63a43239e459334c76b bug, sounds like a good workaround, will do it. |
the case is calling |
Platform:
compileSdkVersion 30
targetSdkVersion 30
Device API: Galaxy S8, Android 9
IDE:
4.3
Build system:
7.0.1
Android Gradle Plugin:
4.2.2
Sentry Android Gradle Plugin:
2.1.5
Proguard/R8:
Platform installed with:
The version of the SDK:
5.3.0
I have the following issue:
Steps to reproduce:
Could not reproduce on Android 11, but it happens 100% of the time on Android 9 (any manufacturer).
Let me know if you need more info.
Actual result:
Expected result:
This is a different from this crash: #1780
The text was updated successfully, but these errors were encountered: