I started using setCustomKey in the Crashlytics library.
Unfortunately, the current implementation has some serious issue: the order of parameters in setCustomKey is wrong.
It seems like the current implementation was done wrong because of the difference between Android (key, value) and iOS (value, key) Firebase libraries.
Hello!
I started using setCustomKey in the Crashlytics library. Unfortunately, the current implementation has some serious issue: the order of parameters in setCustomKey is wrong.
Here is the code from my app:
Here is the result in Crashlytics report:
Here is the Firebase documentation:
It seems like the current implementation was done wrong because of the difference between Android (key, value) and iOS (value, key) Firebase libraries.