android – Serializing to a byte array threw an IOException (should never happen)-ThrowExceptions

Exception or error:

I have this new error from one user. This happened when I pushed the app with the new 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)

I have no idea were to start.

How to solve:

I’m an engineer from Firebase Performance Monitoring. Sorry to everyone that’s encountered this issue. We’ve identified the problem and a patch is now available. Please upgrade to 11.0.2.

###

EDIT: Firebase 11.0.2 seems to have fixed the issue for me

Initial answer:
I had the same issue on a Galasy SIII running 4.4 (CyanogenMod).
I think the issue can be resolved by removing the AddTrace annotations.

However, reverting Firebase to 10.2.6 fixed the issue for me, even if using the annotations.

I have submitted a bug report to the Firebase team as asked by Eric Shieh (https://firebase.google.com/support/contact/bugs-features)

Leave a Reply

Your email address will not be published. Required fields are marked *