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

Asked 8/6, 2017 at 12:9 Answered 22/6, 2017 at 19:2

Solved android firebase google-play-services firebase-performance

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.

Pedicle answered 8/6, 2017 at 12:9 Comment(15)

Where this exactly happen? can you post some code? – Stopgap 8/6, 2017 at 23:38

I don't know! This is what I get from Fabric. – Pedicle 9/6, 2017 at 18:18

I have the same in emulator. There're multiple warnings in log: W/GooglePlayServicesUtil: Google Play services out of date. Requires 11010000 but found 10930876 – Extractor 10/6, 2017 at 22:52

I think is regarding the Firebase Perf tools – Pedicle 10/6, 2017 at 23:22

Got the same issue, but not only with 1 user. Version rolled out to 200 users, and so far 14.2% are affected by this. Version 11.0.0 for firebase as well as play services. – Falchion 13/6, 2017 at 16:4

Do you have Firebase Perf tools added? – Pedicle 13/6, 2017 at 16:7

Yes. I'll see tomorrow what happens if I kick it out again. – Falchion 13/6, 2017 at 16:17

You won't get the error anymore :)) – Pedicle 13/6, 2017 at 16:26

True, looks like it so far. Staged rollout is proceeding, so far no crashes. Well, guess that's why it's in beta. – Falchion 14/6, 2017 at 10:8

I also see it, reported this bug to the Firebase team. Will update you on resolution. – Elum 15/6, 2017 at 10:26

I have the same issue. It seems to be a problem only on Android N (no access to O to test) – Cryo 15/6, 2017 at 16:37

Rumor is Firebase 11.0.1 will fix this. – Cumulostratus 16/6, 2017 at 21:28

For those seeing this issue, please reach out to firebase.google.com/support/contact/bugs-features and include dependencies from your gradle build files if you can. Glad to see interest in Firebase Performance and appreciate your patience! – Kight 17/6, 2017 at 18:19

11.0.1 does not fix the issue ... started a staged rollout yesterday with 11.0.1 and 22% of those users get this crash. – Pasteurize 22/6, 2017 at 18:17

I'm an engineer from Firebase Performance Monitoring. Sorry to everyone that's encountered this issue. We've identified the issue and are working on a fix. Until the patch is released, the workarounds are: 1) Disable automated instrumentation and only use the tracing API 2) Dow – Starlastarlene 22/6, 2017 at 18:59

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.

Starlastarlene answered 22/6, 2017 at 19:2 Comment(3)

Do we also need to update the firebase-plugins? Also, lints for updates would be great – Rubricate 30/6, 2017 at 9:44

Updating the plugin is not needed in this case. – Kight 5/7, 2017 at 18:36

An indicator that your SDK is out of date is a great idea. We've put that on our roadmap – Starlastarlene 10/7, 2017 at 16:30

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)

Counterweigh answered 19/6, 2017 at 10:23 Comment(0)

Recommended topics

Hot tags