Question

我有来自一个用户的这个新错误。当我使用新的11.0.0 Play Services推送应用程序时，就会发生这种情况。

Fatal Exception: java.lang.RuntimeException: Serializing to a byte array threw an IOException (should never happen).
       at com.google.android.gms.internal.aif.zzn(Unknown Source)
       at com.google.android.gms.internal.aez.zzKB(Unknown Source)
       at com.google.android.gms.internal.aez.zzKC(Unknown Source)
       at com.google.android.gms.internal.aez.zzKB(Unknown Source)
       at com.google.android.gms.internal.afc.run(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:762)
Caused by com.google.android.gms.internal.ahy: CodedOutputStream was writing to a flat byte array and ran out of space (pos 199 limit 199).
       at com.google.android.gms.internal.ahx.zze(Unknown Source)
       at com.google.android.gms.internal.ahx.zzc(Unknown Source)
       at com.google.android.gms.internal.ahx.zzc(Unknown Source)
       at com.google.android.gms.internal.ahx.zzb(Unknown Source)
       at com.google.android.gms.internal.afq.zza(Unknown Source)
       at com.google.android.gms.internal.ahx.zzJ(Unknown Source)
       at com.google.android.gms.internal.ahx.zzJ(Unknown Source)
       at com.google.android.gms.internal.afr.zza(Unknown Source)
       at com.google.android.gms.internal.aif.zzn(Unknown Source)
       at com.google.android.gms.internal.aez.zzKB(Unknown Source)
       at com.google.android.gms.internal.aez.zzKC(Unknown Source)
       at com.google.android.gms.internal.aez.zzKB(Unknown Source)
       at com.google.android.gms.internal.afc.run(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:762)

我不知道要开始。

Answer 1

我是Firebase Performance Monitoring的工程师。对于遇到此问题的每个人都很抱歉。我们已经确定了问题，现在可以使用补丁。请升级到11.0.2。

Answer 2

编辑：Firebase 11.0.2似乎已经解决了我的问题

初步答复：我在运行4.4（CyanogenMod）的Galasy SIII上遇到了同样的问题。我认为可以通过删除AddTrace注释来解决该问题。

但是，即使使用注释，将Firebase还原为10.2.6也会解决我的问题。

我已按照Eric Shieh（https://firebase.google.com/support/contact/bugs-features）的要求向Firebase小组提交了错误报告

序列化为字节数组会引发IOException（应该永远不会发生）

2 个答案: