Skip to content

Fatal Exception: java.lang.SecurityException - Binder invocation to an incorrect interface #44

@qwexter

Description

@qwexter

Hi! I see a lot of crashes on start of my app via Crashlytics. They are similar but crashed in different activity on app start.

Fatal Exception: java.lang.SecurityException Binder invocation to an incorrect interface
android.os.Parcel.readException (Parcel.java:1959) android.os.Parcel.readException (Parcel.java:1905) android.support.customtabs.ICustomTabsService$Stub$Proxy.warmup (ICustomTabsService.java:294) androidx.browser.customtabs.CustomTabsClient.warmup (CustomTabsClient.java:176) **saschpe.android.customtabs.CustomTabsHelper$bindCustomTabsService$myConnection$1.onCustomTabsServiceConnected (CustomTabsHelper.java:2)** androidx.browser.customtabs.CustomTabsServiceConnection.onServiceConnected (CustomTabsServiceConnection.java:57) android.app.LoadedApk$ServiceDispatcher.doConnected (LoadedApk.java:1656) android.app.LoadedApk$ServiceDispatcher$RunConnection.run (LoadedApk.java:1685) android.os.Handler.handleCallback (Handler.java:789) android.os.Handler.dispatchMessage (Handler.java:98) android.os.Looper.loop (Looper.java:164) android.app.ActivityThread.main (ActivityThread.java:6938) java.lang.reflect.Method.invoke (Method.java) com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327) com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)
Right now i think remove warm up feature. I hope it solve this crash right now.
Top of crashed vendors - Samsung (S10, a6, a50, s9), OnePlus, Nokia, Xiaomi, Huawei.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions