Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Crashlytics vs Fabric vs Firebase Crash Reporting — I'm lost

Tags:

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'

like image 375
Pavel Alexeev Avatar asked Sep 27 '18 19:09

Pavel Alexeev


People also ask

What happened to Crashlytics?

In January 2017, Crashlytics and Fabric were acquired by Google. In September 2018, Google announces that Fabric will be deprecated and developers should use Crashlytics via Firebase.

Is Crashlytics deprecated?

We are writing to let you know that the Fabric Crashlytics SDK is now deprecated and will continue reporting your app's crashes until November 15, 2020. After this date, the Fabric Crashlytics SDK and beta versions of the Firebase Crashlytics SDK will stop sending crash reports for your app.

How do I find out crashes in Firebase Crashlytics?

Open your app from the home screen of your test device or simulator. In your app, press the "Test Crash" button that you added using the code above. After your app crashes, run it again from Xcode so that your app can send the crash report to Firebase.

Is Crashlytics GDPR compliant?

This means that, under the GDPR, it isn't necessary or appropriate to seek a user's consent to transfer their data outside of the EU for the purposes of using Crashlytics.


1 Answers

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!

Crashlytics Setup

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.

like image 121
Pavel Alexeev Avatar answered Sep 22 '22 23:09

Pavel Alexeev