<small id='GweQX'></small><noframes id='GweQX'>

    <legend id='GweQX'><style id='GweQX'><dir id='GweQX'><q id='GweQX'></q></dir></style></legend>
    <tfoot id='GweQX'></tfoot>
      <bdo id='GweQX'></bdo><ul id='GweQX'></ul>
  1. <i id='GweQX'><tr id='GweQX'><dt id='GweQX'><q id='GweQX'><span id='GweQX'><b id='GweQX'><form id='GweQX'><ins id='GweQX'></ins><ul id='GweQX'></ul><sub id='GweQX'></sub></form><legend id='GweQX'></legend><bdo id='GweQX'><pre id='GweQX'><center id='GweQX'></center></pre></bdo></b><th id='GweQX'></th></span></q></dt></tr></i><div id='GweQX'><tfoot id='GweQX'></tfoot><dl id='GweQX'><fieldset id='GweQX'></fieldset></dl></div>

    1. Firebase 消息传递 - “警报太多"在三星的安卓设备上

      时间:2024-08-24

    2. <tfoot id='ZxPLP'></tfoot>
        <tbody id='ZxPLP'></tbody>

      <small id='ZxPLP'></small><noframes id='ZxPLP'>

          • <bdo id='ZxPLP'></bdo><ul id='ZxPLP'></ul>
            <i id='ZxPLP'><tr id='ZxPLP'><dt id='ZxPLP'><q id='ZxPLP'><span id='ZxPLP'><b id='ZxPLP'><form id='ZxPLP'><ins id='ZxPLP'></ins><ul id='ZxPLP'></ul><sub id='ZxPLP'></sub></form><legend id='ZxPLP'></legend><bdo id='ZxPLP'><pre id='ZxPLP'><center id='ZxPLP'></center></pre></bdo></b><th id='ZxPLP'></th></span></q></dt></tr></i><div id='ZxPLP'><tfoot id='ZxPLP'></tfoot><dl id='ZxPLP'><fieldset id='ZxPLP'></fieldset></dl></div>

                <legend id='ZxPLP'><style id='ZxPLP'><dir id='ZxPLP'><q id='ZxPLP'></q></dir></style></legend>
                本文介绍了Firebase 消息传递 - “警报太多"在三星的安卓设备上的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

                问题描述

                我们在 Android 应用中使用 Firebase 消息传递,自上周以来,我们报告了许多三星设备的崩溃.该问题与我们的任何课程都无关.我们没有使用 AlarmManager 等.

                We are using Firebase Messaging in Android app and since last week we reported many crashes from Samsung devices. The problem is not related with any of our classes. We are not using AlarmManager etc.

                这里是堆栈跟踪:

                1) Parcel.java

                1) Parcel.java

                Fatal Exception: java.lang.SecurityException: !@Too many alarms (500) registered from pid 13776 uid 10011
                   at android.os.Parcel.readException(Parcel.java:1540)
                   at android.os.Parcel.readException(Parcel.java:1493)
                   at android.app.IAlarmManager$Stub$Proxy.set(IAlarmManager.java:206)
                   at android.app.AlarmManager.setImpl(AlarmManager.java:428)
                   at android.app.AlarmManager.set(AlarmManager.java:215)
                   at com.google.firebase.iid.FirebaseInstanceIdService.zzah(Unknown Source)
                   at com.google.firebase.iid.FirebaseInstanceIdService.zzag(Unknown Source)
                   at com.google.firebase.iid.FirebaseInstanceIdService.zzag(Unknown Source)
                   at com.google.firebase.iid.FirebaseInstanceIdService.zzm(Unknown Source)
                   at com.google.firebase.iid.zzb$2.run(Unknown Source)
                   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
                   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
                   at java.lang.Thread.run(Thread.java:818)
                

                2) 在 Binder.java 中

                2) In Binder.java

                Fatal Exception: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in com.google.firebase.iid.FirebaseInstanceIdService$1@12533ba
                   at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:891)
                   at android.os.Handler.handleCallback(Handler.java:746)
                   at android.os.Handler.dispatchMessage(Handler.java:95)
                   at android.os.Looper.loop(Looper.java:148)
                   at android.app.ActivityThread.main(ActivityThread.java:5443)
                   at java.lang.reflect.Method.invoke(Method.java)
                   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
                   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
                Caused by java.lang.RuntimeException: Failure from system
                   at android.app.ContextImpl.sendBroadcast(ContextImpl.java:772)
                   at android.content.ContextWrapper.sendBroadcast(ContextWrapper.java:396)
                   at com.google.firebase.iid.FirebaseInstanceIdService$1.onReceive(Unknown Source)
                   at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:881)
                   at android.os.Handler.handleCallback(Handler.java:746)
                   at android.os.Handler.dispatchMessage(Handler.java:95)
                   at android.os.Looper.loop(Looper.java:148)
                   at android.app.ActivityThread.main(ActivityThread.java:5443)
                   at java.lang.reflect.Method.invoke(Method.java)
                   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
                   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
                Caused by android.os.DeadObjectException
                   at android.os.BinderProxy.transactNative(Binder.java)
                   at android.os.BinderProxy.transact(Binder.java:503)
                   at android.app.ActivityManagerProxy.broadcastIntent(ActivityManagerNative.java:3075)
                   at android.app.ContextImpl.sendBroadcast(ContextImpl.java:767)
                   at android.content.ContextWrapper.sendBroadcast(ContextWrapper.java:396)
                   at com.google.firebase.iid.FirebaseInstanceIdService$1.onReceive(Unknown Source)
                   at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:881)
                   at android.os.Handler.handleCallback(Handler.java:746)
                   at android.os.Handler.dispatchMessage(Handler.java:95)
                   at android.os.Looper.loop(Looper.java:148)
                   at android.app.ActivityThread.main(ActivityThread.java:5443)
                   at java.lang.reflect.Method.invoke(Method.java)
                   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
                   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
                

                你有类似的问题吗?你知道什么可能是一个潜在的问题吗?我正在使用 firebase@9.6.1

                Do you have similar problems? Do you know what could be a potential problem? I'm using firebase@9.6.1

                推荐答案

                好消息!借助 last update 10.0,firebase 团队解决了 三星设备中的警报太多,这是补丁说明:

                Good news! With the last update 10.0 the firebase team solved the problems with Too many alarms in Samsung devices, this is the patch note:

                已修复 - 导致错误设置额外警报的问题,从而导致在某些三星设备上的堆栈跟踪中出现过多警报而崩溃.

                Fixed - An issue that caused extra alarms to be incorrectly set, resulting in crashes with Too Many Alarms in the stack trace on some Samsung devices.

                编程不错!

                这篇关于Firebase 消息传递 - “警报太多"在三星的安卓设备上的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                上一篇:Java Firebase 云消息.向所有人发送消息 下一篇:应用程序在后台时的 Android 通知

                相关文章

                  <bdo id='h2cZG'></bdo><ul id='h2cZG'></ul>

              1. <small id='h2cZG'></small><noframes id='h2cZG'>

                  <legend id='h2cZG'><style id='h2cZG'><dir id='h2cZG'><q id='h2cZG'></q></dir></style></legend>

                  1. <i id='h2cZG'><tr id='h2cZG'><dt id='h2cZG'><q id='h2cZG'><span id='h2cZG'><b id='h2cZG'><form id='h2cZG'><ins id='h2cZG'></ins><ul id='h2cZG'></ul><sub id='h2cZG'></sub></form><legend id='h2cZG'></legend><bdo id='h2cZG'><pre id='h2cZG'><center id='h2cZG'></center></pre></bdo></b><th id='h2cZG'></th></span></q></dt></tr></i><div id='h2cZG'><tfoot id='h2cZG'></tfoot><dl id='h2cZG'><fieldset id='h2cZG'></fieldset></dl></div>
                  2. <tfoot id='h2cZG'></tfoot>