π΅οΈββοΈ Crash Investigators!
We collaborated with a cartoonist to produce a comic about a crash detective solving crashes with Firebase @Crashlytics. Does she solve the mystery case?
Read here to find out β https://t.co/KjwCrdPZZN
@Nathan_Mellor@Firebase Thanks Nathan, we haven't seen other reports of this, but think it may be due to interacting crash handlers. Can you submit a support ticket? We'd really like to look into it :) -Todd
@dknchris@Firebase Thanks! The team put a lot of effort into dashboard improvements, and we definitely aren't done yet! Appreciate the feedback about Play requirements, will bring up with team :) -Todd
@amIT_singh29@adamlondero@Firebase@fabric Thanks. I would put it in the range of months, however we cannot pin down a specific date. Thanks for holding us to our word. -Todd
@_pot8os Thanks for reaching out. This script makes a settings request when you build your app the first time and uploads symbols. I suspect you won't run into specific issues if you remove it, but make sure you have dSYMs setup to upload for debug builds.
iOS crash processing in Crashlytics has been restored to 100% as of May 8 at 7:00 PM UTC. Thank you for your support (and humor) as we worked to resolve this issue.
@EastonTao Yes, Crashlytics and Google Analytics work in China for Android and iOS both! Some other Firebase services require Google Play and therefore will not work.
Due to a major increase in crashes across the iOS ecosystem caused by an issue with a popular iOS SDK, iOS crash processing in Crashlytics was disabled at 11:00 PM UTC. We are actively working to return processing to normal. Visit our status dashboard for the latest updates.
@subdan_@Firebase Hi Danniil, sorry to hear that you are running into an issue. Can you DM me? You can also check out our static frameworks here: https://t.co/KotHrvAtlq