序列化为字节数组抛出 IOException(永远不应该发生)

Serializing to a byte array threw an IOException (should never happen)

我收到一位用户的新错误。当我使用新的 11.0.0 Play 服务推送应用程序时发生了这种情况。

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)

我不知道要开始了。

编辑:Firebase 11.0.2 似乎已经为我解决了这个问题

初始答案: 我在 Galasy SIII 运行 4.4 (CyanogenMod) 上遇到了同样的问题。 我认为这个问题可以通过删除 AddTrace 注释来解决。

但是,将 Firebase 恢复到 10.2.6 对我来说解决了这个问题,即使使用注释也是如此。

我已经按照 Eric Shieh 的要求向 Firebase 团队提交了错误报告 (https://firebase.google.com/support/contact/bugs-features)

我是 Firebase Performance Monitoring 的一名工程师。对遇到此问题的所有人表示抱歉。我们已经确定了问题,现在可以使用补丁。请升级到 11.0.2.