3

As the title, I need to migrate all existing data from Fabric's Crashlytics to Firebase.

The problem here is after migrating, If I remove fabric key in AndroidManifest, My app can't push the crash report to firebase's Crashlytics anymore. But when I create Firebase's Crashlytics from the beginning (without Fabric migrate) They recommend me to remove existing Fabric key to make it work.

Is it ok?

Trieu Le Hai
  • 57
  • 7

1 Answers1

3

Mike from Fabric here. Yes, now is a good time to start linking and migrating to Firebase.

Mike Bonnell
  • 16,181
  • 3
  • 61
  • 77
  • Can you explain more detail? So how can I have that kind of data without app linking? – Trieu Le Hai Apr 11 '18 at 02:48
  • If you're currently using Crashlytics via Fabric, then data will flow there. If you're using Firebase Crashlytics, then data would show up there. – Mike Bonnell Apr 11 '18 at 16:13
  • Oh got it. At this moment, I'm linking Fabric with Firebase, and the data shows up in both place. What happens if one day Fabric shut down its Crashlytics service, will my crash report continues to show up on Firebase with current configuration? – Trieu Le Hai Apr 13 '18 at 02:44
  • Gotcha, if you're doing a combined setup, then you would see data in both places. Given your current configuration it sounds like you would be all set. – Mike Bonnell Apr 13 '18 at 14:34
  • I have also done the linking but now I want to turn off Fabric, and removing the meta-data from the Manifest doesn't do the thing. How can I get the reports only on Fabric? – f.trajkovski Dec 12 '18 at 16:07
  • 1
    After migration completed application stop sending the crash report to fabric and firebase crashlytics dashboard – blackjack Sep 19 '19 at 07:02
  • Contact the support folks if you have issues post-migration as they can dig deeper into this. – Mike Bonnell Sep 30 '19 at 14:05