Why do we use fabric for crashlytics?

[Acetyld]

Hello!

As the title states: "Why do we use fabric for crashlytics?" and not the new crashlytics library https://firebase.google.com/docs/crashlytics/get-started-new-sdk?platform=android

[Ehesp]

We haven't got around to updating the library yet to remove fabric.

[Acetyld]

So fabric is not needed? Or is the documentation wrong, or havent you implemented the firebase way yet?

[mikehardy]

Fabric is needed
The Firebase Crashlytics is still in beta.

I think the upstream Google Firebase SDK team is doing a poor job messaging this thing really.

They have put out that Fabric is out of support very shortly and you should migrate. But it is unclear to what so people are naturally very concerned, but they are all asking why we haven't migrated to a beta library. Isn't that odd?

If I understand correctly there are three crashlytics:

1. Fabric Fabric Crashlytics - from before Firebase/Google bought them. This is going away. You need to migrate
2. Firebase Fabric Crashlytics - this is the current stable thing. It's what react-native-firebase uses. I can't see how this would be going away yet since the future option is still beta?
3. Firebase Crashlytics - this is in beta. It's the future but the future isn't here yet (or it wouldn't be beta?). I understand google pushes beta stuff out widely frequently but to actually discontinue option 1 before option 3 is out of beta seems bizarre.

So I think everyone is fine for now, with option 2, and it's what react-native-firebase uses for now.

Anyone have info to the contrary? I would love to hear it

[embpdaniel]

@mikehardy Is there a diff between the Fabric service vs the Fabric SDK? My understanding is that option 2 you mentioned, uses the Fabric SDK but doesn't have to be linked with the Fabric service which is deprecated. It could be, but it's optional. Is this correct?

[mikehardy]

That's my understanding - that using Fabric SDK but with Firebase back-end, and why I'm okay with react-native-firebase using the Fabric SDK vs converting to a beta (in form of option 3 above) SDK, and why I think Firebase has some poor messaging here. This shouldn't be a question, we should all understand this clearly from their docs. Instead we have lots of worried devs thinking they're deprecated and have some action to take, when they're (I think) safely using Option 2

[r0b0t3d]

Just got an email from Fabric. As @mikehardy mention above, if you are using Fabric Fabric Crashlytics(1), you need to migrate your project to Firebase Fabric Crashlytics (2)

[deecewan]

Update here:

The top of this page now has:

The upgrade guide now mentions to remove the Fabric and Crashlytics pods, and replace with Firebase/Crashlytics. I think that means that it is out of beta 🤷

But also. It was last updated on 2020-05-07 (6 days ago) so I'm not sure it's super critical

[mikehardy]

Yep - it left beta on April 21 https://firebase.google.com/support/release-notes/ios#version_6230_-_april_21_2020 (April 23 for Android https://firebase.google.com/support/release-notes/android#crashlytics_v17-0-0)

And there's a PR to port to it #3580 which I think looks pretty good and is just waiting review from one of @Salakar or @Ehesp ?

I actually think it is super critical but I use an "urgent / not urgent" axis and a "important / not important" axis to make sure the "important but not urgent" stuff doesn't get lost. This is in that quadrant - if we don't address it, we'll all be sad when it is urgent and important and not done yet :-), so I I'm hoping it gets nailed while still not urgent - I think it will

[deecewan]

yup - just found the PR and had a look through. was about to tackle it myself, but (luckily) decided to check if someone else had started first.

I guess when I said "not super critical" i was talking on the "urgent/not urgent" axis.

[mikehardy]

Thanks for reviewing it - I saw your comment over there, looked spot on. Shouldn't be long now before that's shaped up and merged either way. Cheers!

[Salakar]

Commented on the PR with more info / blockers, but I'm hoping to pickup fully on Friday.

[stale]

Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.