I have upgraded to the latest Firebase Crashlytics version for my Xamarin.Forms iOS app. But still I couldn't see the crashes getting logged in the Firebase Console. This is the message I see in the Console : > As of November 16, we are only processing crashes from the Firebase iOS SDK 4.0.0+. As a result, you might be seeing no new crashes in your dashboard.
I'm thinking of testing it by implementing a test crash, but I don't know the code as to how to do this..
So, I'm desperately in need of a documentation/link that guides me on how to log events / try a test crash to Firebase Crashlytics in Xamarin.Forms. Any help is much appreciated. Thanks in advance.
I'm using latest stable version of Xamarin.Firebase.iOS.Crashlytics version : v4.6.2
Thank you JESUS for His help!
Adding this line worked : Crashlytics.SharedInstance.Init();
I couldn't find any details on this initialization code in Google. If there had been these details in official documentation / readme in appropriate Github repo after v4.6.2 release, it could have been much easier and time saving for me. This is my concern
Thank you JESUS..!! This issue is resolved.
Don't know why.. After uninstalling CarouselView.FormsPlugin package, the logs went off. Crashes are now reported properly
Maybe some error handling is being done in the CarouselView.FormsPlugin package.
While testing each crash, I only got this CarouselView.FormsPlugin named exception being reported in the Firebase console. In that way, I identified that this package is interfering with the Crashlytics reporting as displayed in the logs.
I was using CarouselView.FormsPlugin v5.2.0
Answers
First We need to add a GoogleService-Info.plist and Xamarin.Firebase.iOS.Core NuGet to the iOS project , then call the initial code , you could refer to the detailed steps here : https://stackoverflow.com/a/58008300/8187800 .
Xamarin Community forum will be migrating to a new home on Microsoft Q&A!
We invite you to post new questions in the Xamarin forum’s new home on Microsoft Q&A!
For more information, please refer to the sticky post.
Thanks @ColeX . I had Crashlytics working in its older SDK version.
In the VS2019 output window, I could see that the Firebase.Crashlytics.dll assembly is not loaded though the package is installed but Core, Analytics, Installations.dll does..
Is there anything wrong in my initialization?
I've just called this - Firebase.Core.App.Configure();
Crashlytics.Configure (); is not required now. Is there any other line of code required for initializing Crashlytics? I'm using Crashlytics v4.6.2
Thank you JESUS for His help!
Adding this line worked :
Crashlytics.SharedInstance.Init();
I couldn't find any details on this initialization code in Google. If there had been these details in official documentation / readme in appropriate Github repo after v4.6.2 release, it could have been much easier and time saving for me. This is my concern
Facing dsym missing issue i am using v4.6.2.
I followed below steps to integrate crashlytics. Included folowing packageges
Xamarin.Firebase.iOS.Analytics (6.9.0)
Xamarin.Firebase.iOS.Core (6.10.4)
Xamarin.Firebase.iOS.Crashlytics (4.6.2)
appdelegate didfinish launch
Firebase.Core.App.Configure();
Crashlytics.SharedInstance.Init();
I have used mtouch arguement --dsym=yes and Extra mlaunch argument as --argument=-FIRDebugEnabled
Still same error!! Upload 2 missing dSYMs required to process 13 crashes
Hi @Priyam , you're not getting the blue notification in Firebase Console after initializing Crashlytics?
Though crash count is increasing for me after initialization, still the stack trace of the crashes are not logged. All crashes are coming under the same stack trace with increased count though the exceptions are different.
I get the following logs in Visual Studio which makes me think that something else is interfering, but though I tried, I couldn't find what is interfering with Crashlytics :
I'm not using any other crash reporting service
Other Analytics SDKs I'm using
I also tried this solution - https://stackoverflow.com/a/42421085/10329199
Thank you JESUS..!! This issue is resolved.
Don't know why.. After uninstalling CarouselView.FormsPlugin package, the logs went off. Crashes are now reported properly
Maybe some error handling is being done in the CarouselView.FormsPlugin package.
While testing each crash, I only got this CarouselView.FormsPlugin named exception being reported in the Firebase console. In that way, I identified that this package is interfering with the Crashlytics reporting as displayed in the logs.
I was using CarouselView.FormsPlugin v5.2.0