It started few days later when we launched an ad campaign which brought lots of Android users. It never happened on our testing devices (10+ Android models).
So far it happened only on Android devices
We are seeing other crashes on our app, but nothing compared to the scale of this one (the worst bug had something like 200 occurrences, this one had 1.500+ occurrences)
One question though: is there a way to filter crash reports? Is annoying to still go through bug reports that are already fixed in the current release.
we implemented it in one of our top apps and we are getting something like 3/4.000 bugs report of this bug. Plus we found this new one, which has more informations (around 2/400 times a day) :
If I presume you’re using Unity 5.x and the latest plugin then, this certainly seems like a race condition in the plugin and something we need to fix on our end. I’ll let our editor guy know! Thanks for the report!
I hope, other than the spam from this one exception, you’re also seeing others?
Cool, thanks for letting us know! Yeah, sadly there isn’t a good way to determine the plugin version at the moment. If you reimported it, then you have the latest at the moment.
Sorry to re-open the thread, but we’re currently having the same issues as well.
Details:
Unity: 5.2.3p1
UnityCrashLog md5: d57968508ec492be1a5473689d6b5e3d (gives the date modified as Aug 24th)
Currently we’re only on Android, but we’ve > 1000 instances of it so far across a number of devices (TCL 5042T (Android 4.4.4), Sony D6603 (Android 5.1.1), SGH-I337M (Android 5.0.1)). We’re still in soft-launch, so we don’t have a huge number of users, so it’s almost certainly a small number repeatedly triggering the error.
I can reliably recreate this in 5.3.4 in the editor by trying to initialize crash logging while my laptop is connected to wifi, but my router is disconnected.