rudderlabs / rudder-sdk-android

Android SDK for RudderStack - the Customer Data Platform for Developers.
https://www.rudderstack.com
Other
18 stars 29 forks source link

BUG : Fatal Exception: java.lang.NullPointerException Attempt to read from field 'java.lang.Object za.b.a' on a null object reference #370

Closed AndreasBoehm closed 6 months ago

AndreasBoehm commented 8 months ago

Describe the bug I just found this crash in our crashlytics dashboard.

To Reproduce Can't provide steps.

Version of the Android SDK Android SDK v1.21.0

SDK initialisation snippet

apiKey?.let {
            rudderClient = RudderClient.getInstance(
                context,
                it,
                RudderConfig.Builder()
                    .withDataPlaneUrl(dataPlaneUrl)
                    .withTrackLifecycleEvents(true)
                    .withRecordScreenViews(false)
                    .withLogLevel(logLevel)
                    .build()
            )
        }

Stacktrace

Fatal Exception: java.lang.NullPointerException: Attempt to read from field 'java.lang.Object za.b.a' on a null object reference
       at com.rudderstack.android.sdk.core.RudderUserSessionManager.getSessionId(RudderUserSessionManager.java:76)
       at com.rudderstack.android.sdk.core.RudderUserSessionManager.applySessionTracking(RudderUserSessionManager.java:43)
       at com.rudderstack.android.sdk.core.EventRepository.processMessage(EventRepository.java:340)
       at com.rudderstack.android.sdk.core.RudderClient.dumpMessage(RudderClient.java:536)
       at com.rudderstack.android.sdk.core.RudderClient.track(RudderClient.java:223)
       at com.rudderstack.android.sdk.core.RudderClient.track(RudderClient.java:247)
itsdebs commented 8 months ago

Can you please try 1.21.1? We have fixed a race condition that might cause this issue.

desusai7 commented 7 months ago

@AndreasBoehm, Have you tried updating to the latest version?

And did this issue get resolved for you ?

1abhishekpandey commented 6 months ago

Hey @AndreasBoehm, I wanted to inform you that I'm closing this issue as it has been inactive for a significant period of time. While we haven't received any updates or responses regarding this issue, please know that you're always welcome to reopen it if you encounter the problem again or have any additional information to share. Your feedback is valuable to us, and we want to ensure that all issues are addressed promptly.