search

muxinc / mux-stats-sdk-bitmovin-android

Apache License 2.0
0 stars 1 forks source link

NullPointerException on 0.5.3 with Bitmovin Player #13

Open Grandpasoul opened 1 year ago

Grandpasoul commented 1 year ago

Hello again

We are having some crashes from MUX sdk verion 0.5.3 with Bitmovin Player 3.24.1 since January 23rd.

From a pool of 44k users, is not so serious, but we want to check what is the problem

Here is the stacktrace:

Exception java.lang.NullPointerException:
  at com.mux.stats.sdk.muxstats.bitmovinplayer.MuxStatsSDKBitmovinPlayer.lambda$new$12$com-mux-stats-sdk-muxstats-bitmovinplayer-MuxStatsSDKBitmovinPlayer (MuxStatsSDKBitmovinPlayer.java:267)
  at com.mux.stats.sdk.muxstats.bitmovinplayer.MuxStatsSDKBitmovinPlayer$$ExternalSyntheticLambda13.onEvent
  at com.bitmovin.player.api.event.EventEmitter$DefaultImpls$d.a (SourceFile:1)
  at com.bitmovin.player.api.event.EventEmitter$DefaultImpls$d.invoke (SourceFile:1)
  at com.bitmovin.player.u.b.b (SourceFile:206)
  at com.bitmovin.player.u.d.a (SourceFile:1)
  at com.bitmovin.player.b.r0.b (SourceFile:4)
  at com.bitmovin.player.b.r0.a (SourceFile:19)
  at com.bitmovin.player.b.r0.c (SourceFile:5)
  at com.bitmovin.player.b.s0.b (SourceFile:8)
  at com.bitmovin.player.a.e.a (SourceFile:217)
  at com.bitmovin.player.a.e.a (SourceFile:4)
  at com.bitmovin.player.a.e$c.a (SourceFile:1)
  at com.bitmovin.player.a.e$c.invoke (SourceFile:1)
  at com.bitmovin.player.u.b.b (SourceFile:206)
  at com.bitmovin.player.u.d.a (SourceFile:1)
  at com.bitmovin.player.i.p.a (SourceFile:13)
  at com.bitmovin.player.f.c0.k (SourceFile:9)
  at com.bitmovin.player.f.c0.play (SourceFile:1)
  at com.bitmovin.player.f.i.play (SourceFile:1)
  at com.bitmovin.player.a.b.play (SourceFile:1)
  at com.bitmovin.player.a.e.play
  at com.bitmovin.player.a.g.playAd (SourceFile:1)
  at com.google.ads.interactivemedia.v3.internal.akf.f (IMASDK:6)
  at com.google.ads.interactivemedia.v3.internal.ajx.r (IMASDK:3)
  at com.google.ads.interactivemedia.v3.internal.ajx.k (IMASDK:117)
  at com.google.ads.interactivemedia.v3.internal.ake.f (IMASDK:6)
  at com.google.ads.interactivemedia.v3.internal.aka.onPostMessage (IMASDK:2)
  at androidx.webkit.internal.WebMessageListenerAdapter.onPostMessage (WebMessageListenerAdapter.java:54)
  at java.lang.reflect.Method.invoke
  at org.chromium.support_lib_boundary.util.BoundaryInterfaceReflectionUtil$InvocationHandlerWithDelegateGetter.invoke (BoundaryInterfaceReflectionUtil.java:162)
  at java.lang.reflect.Proxy.invoke (Proxy.java:1006)
  at $Proxy14.onPostMessage
  at org.chromium.android_webview.WebMessageListenerHolder.onPostMessage (chromium-TrichromeWebViewGoogle.aab-stable-<US_SOCIAL_SECURITY_NUMBER>:53)
  at android.os.MessageQueue.nativePollOnce
  at android.os.MessageQueue.next (MessageQueue.java:335)
  at android.os.Looper.loopOnce (Looper.java:186)
  at android.os.Looper.loop (Looper.java:313)
  at android.app.ActivityThread.main (ActivityThread.java:8741)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1067)

And here are the top devices having the problem

Captura de pantalla 2023-02-03 a la(s) 11 41 34

Let me know if you need another data Cheers.

Grandpasoul commented 1 year ago

The issue still appears on some devices, last month we had 100 events related to this. Stacktrace is the same.

Captura de pantalla 2023-04-18 a la(s) 10 15 06

I'll wait for an answer soon. 2 months have passed and no reply.