plaidev / karte-android-sdk

KARTE SDK for Android
https://karte.io/
Apache License 2.0
5 stars 3 forks source link

WindowManager$BadTokenException - Unable to add window -- token null is not valid; is your activity running? #24

Closed sontnfabbi closed 4 months ago

sontnfabbi commented 5 months ago

Expected Behavior

the crash was reported in firebase

SDK Version

implementation 'io.karte.android:core:2.22.0'
implementation 'io.karte.android:inappmessaging:2.18.0'  //アプリ内メッセージ機能を提供します。
implementation 'io.karte.android:notifications:2.10.0'  //プッシュ通知の受信および効果測定機能を提供します。
implementation 'io.karte.android:visualtracking:2.9.0'

Android Version

All version

Build Environment

Logs

Log from firebase crashlytics ` Fatal Exception: android.view.WindowManager$BadTokenException: Unable to add window -- token null is not valid; is your activity running? at android.view.ViewRootImpl.setView(ViewRootImpl.java:1261) at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:431) at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:110) at io.karte.android.inappmessaging.internal.view.WindowView.showInternal(WindowView.kt:153) at io.karte.android.inappmessaging.internal.view.WindowView.access$getWindowManager$p(WindowView.kt:65) at io.karte.android.inappmessaging.internal.view.WindowView.access$showInternal(WindowView.kt:65) at io.karte.android.inappmessaging.internal.view.WindowView$show$1.run(WindowView.kt:120) at android.os.Handler.handleCallback(Handler.java:938) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:271) at android.app.ActivityThread.main(ActivityThread.java:8305) at java.lang.reflect.Method.invoke(Method.java) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:612) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:992)

`

TakayukiCho commented 4 months ago

This bug is fixed on the newly updated library, InAppMessaging 2.19.1.

For further information, please take a look at our release note.

sontnfabbi commented 4 months ago

ありがとうございました。

This bug is fixed on the newly updated library, InAppMessaging 2.19.1.

For further information, please take a look at our release note.