Crashlytics vs Fabric vs Firebase Crash Reporting — I'm lost
Could someone clarify on these terms? I'm completely lost!
What do Google calls “Crashlytics”, who is Fabric and why it's still not Firebase?
Should I setup crash reporting somewhere in Firebase Console or should I register at Fabric and somehow link accounts?
On iOS what should I use for my very new swift project?
pod 'Firebase/Crash'
or
pod 'Fabric'
or
pod 'Crashlytics'
Answer
OK. So after contacting support I did it!
The problem was that in initial setup (Quality → Crashlytics) when you've being asked “Is this app new to Crashlytics”, you have to choose “My app doesn't have any version of the SDK”.
Even though your app already has latest Crashlytics SDK installed!
Question probably should be “Do this app already use Fabric? —Yes, —No”.
This seems just like a UX error that should be fixed.
As for the terms and history:
- In 2011 there was Crashlytics.
- Also in 2011 there was Firebase.
- In 2013 Twitter acquired Crashlytics
- In 2014 Crashlytics/Twitter announced Fabric – a modular SDK which contains Crashlytics
- In 2014 Google acquired Firebase.
- In 2016 Google introduced Firebase Crash Reporting.
- In 2017 Google acquired Fabric with Crashlytics, deprecate previous Firebase Crash Reporting and now calls its crash analytics service “Crashlytics”.
- In 2020 Fabric is deprecated and “Firebase Crashlytics” is the remaining service. Integrated using
pod 'Firebase/Crashlytics'.
Correct me if I'm wrong.