You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating out version from 4.3.0 up to 4.10.1 we are now seeing a large number of devices that are crashing with this stacktrace
Fatal Exception: java.lang.IllegalAccessError: Interface androidx.lifecycle.FullLifecycleObserver implemented by class com.segment.analytics.AnalyticsActivityLifecycleCallbacks is inaccessible
Have you seen this behavior before? Also, here is the full stacktrace
Fatal Exception: java.lang.IllegalAccessError: Interface androidx.lifecycle.FullLifecycleObserver implemented by class com.segment.analytics.AnalyticsActivityLifecycleCallbacks is inaccessible (declaration of 'com.segment.analytics.AnalyticsActivityLifecycleCallbacks' appears in base.apk!classes3.dex)
at com.segment.analytics.AnalyticsActivityLifecycleCallbacks$Builder.build(AnalyticsActivityLifecycleCallbacks.java:294)
at com.segment.analytics.Analytics.<init>(Analytics.java:351)
at com.segment.analytics.Analytics$Builder.build(Analytics.java:1507)
at com.livesafemobile.nxtenterprise.analytics.SegmentAnalytics$Companion$start$1.onComplete(SegmentAnalytics.java:34)
at com.google.android.gms.tasks.zzi.run(zzi.java:4)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at com.google.android.gms.internal.tasks.zzb.dispatchMessage(zzb.java:6)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8669)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
The text was updated successfully, but these errors were encountered:
this is a new exception. first please update your sdk to the latest 4.10.4, since there is a known NPE in 4.10.1. if the exception still occurs, we will take a look.
After updating out version from 4.3.0 up to 4.10.1 we are now seeing a large number of devices that are crashing with this stacktrace
Have you seen this behavior before? Also, here is the full stacktrace
The text was updated successfully, but these errors were encountered: