For a couple of years now Apple has provided crash reports that are directly available in Xcode (Window > Organizer > Crashes). This opens up the question why the app should continue to include a parallel crash reporting infrastructure (Crashlytics)?
=> Analyze what would be the consequences of getting rid of Crashlytics.
If the decision is made to keep the crash reporting infrastructure, then check out out whether Crashlytics can be replaced with plcrashreporter.
Pros at first glance:
Open source
Clear license
Get rid of the opaque (and therefore suspicious) entanglement of Crashlytics with the Google Analytics platform
Cons at first glance:
Unclear where to store crash reports submitted by plcrashreporter, and how to symbolicate them.
Is it worth replacing one big corp (Google) with another (Microsoft)?
For a couple of years now Apple has provided crash reports that are directly available in Xcode (Window > Organizer > Crashes). This opens up the question why the app should continue to include a parallel crash reporting infrastructure (Crashlytics)?
=> Analyze what would be the consequences of getting rid of Crashlytics.
If the decision is made to keep the crash reporting infrastructure, then check out out whether Crashlytics can be replaced with plcrashreporter.
Pros at first glance:
Cons at first glance: