Hi,
Is there an advantage (or disadvantage) to using Crashlytics now that you can also get crash reports from Apple within Xcode? If they do the same thing I'd rather get rid of the dependency on Crashlytics.
Rob
I am wondering the same. Crashlytics once told me they pass through the crash reports to other handlers. So crashes should show up in both places.
The convinience of fabric emails you when theres a noticable bug. it also emails you everyday the usage stats for your app. In all it generally just offers more. Also you dont have to symbolicate the report to know the call causing the problem or even be near xcode
Matt from Crashlytics here. I'm going to answer this in as fair as way as I can, given my current employer.
I'm currently trying to write an answer here, but constantly getting a "The message contains invalid characters." error. So, please forgive me for answering in parts. Just trying to figure out which pieces the system is unhappy with.
Apple's reports have a number of advantages. First, they aren't impeded by the limitations of a 3rd-party in-process reporter. This allows them to be superior in reliability and timeliness. It is very common for Apple's reporter to find bugs that Crashlytics cannot technically capture. The iOS 9 dynamic loading issue comes to mind. Second, you get it for free, with no dependencies or impact to your app.
My understanding is that to get crash reports in Xcode a user must have enabled (or not disable, can't remember the default) the switch in Settings, under Diagnostics and Usage > Share with App Developers. Is that also the case for Crashlytics?
Rob
That setting is required for Apple reporting, but not for Crashlytics. You can implement privacy within your app, if you'd like. Right now, it looks like about 20-30% of users opt to share reports. Definitely could be a factor in your decision.
Welp, I am completely failing to post my original response. Unsure what's wrong here. But, there are lots of great answers on stackover for this.
