-
Notifications
You must be signed in to change notification settings - Fork 442
Closed
Milestone
Description
[REQUIRED] Please fill in the following fields:
- Unity editor version: 2020.3.13f1
- Firebase Unity SDK version: 8.0.0
- Source you installed the SDK: .unitypackage
- Problematic Firebase Component: Crashlytics
- Other Firebase Components in use: Analytics, RemoteConfig, Messaging
- Additional SDKs you are using: Playfab, ARCore, DevToDev
- Platform you are using the Unity editor on: Windows
- Platform you are targeting: Android
- Scripting Runtime: IL2CPP
[REQUIRED] Please describe the issue here:
We are getting the following error on our Android builds:
Error serializing key/value metadata.
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1441)
at java.util.HashMap$EntryIterator.next(HashMap.java:1475)
at java.util.HashMap$EntryIterator.next(HashMap.java:1473)
at java.util.Collections$UnmodifiableMap$UnmodifiableEntrySet$1.next(Collections.java:1708)
at java.util.Collections$UnmodifiableMap$UnmodifiableEntrySet$1.next(Collections.java:1701)
at org.json.JSONObject.<init>(JSONObject.java:138)
at com.google.firebase.crashlytics.internal.common.p.a(Unknown Source:2)
at com.google.firebase.crashlytics.internal.common.p.a(Unknown Source:7)
at com.google.firebase.crashlytics.internal.common.CrashlyticsController$9.a(Unknown Source:19)
at com.google.firebase.crashlytics.internal.common.CrashlyticsController$9.call(Unknown Source:0)
at com.google.firebase.crashlytics.internal.common.CrashlyticsBackgroundWorker$3.then(Unknown Source:2)
at com.google.android.gms.tasks.h.run(Unknown Source:26)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at com.google.firebase.crashlytics.internal.common.l$1$1.a(Unknown Source:2)
at com.google.firebase.crashlytics.internal.common.b.run(Unknown Source:5)
at java.lang.Thread.run(Thread.java:923)
Steps to reproduce:
Just open the app and this exception will be logged.
We don't know exactly which CustomKey is triggering this issue. It would be very helpful to log which Key had issues when being serialized.
We double-checked and no Keys or values exceed 1024 characters.