question

Paul-9359 avatar image
0 Votes"
Paul-9359 asked RobCaplan edited

Xamarin.Forms - Crashlytics is not logging crashes [Crashlytics 4.6.2]

Hi! I'm using Crashlytics v4.6.2 for my Xamarin.Forms app. Though the crash count is increasing but still no error message/stack trace is logged in the Firebase Console. I tried in release device build as well.

I get the following logs which makes me think that something else is interfering, but though I tried, I couldn't find what is interfering with Crashlytics (if I've perceived it correctly) :

 [Crashlytics] The signal SIGABRT has a non-Crashlytics handler (sigabrt_signal_handler).  This will interfere with reporting.
    
 [Crashlytics] The signal SIGBUS has a non-Crashlytics handler (mono_sigsegv_signal_handler).  This will interfere with reporting.
    
 [Crashlytics] The signal SIGFPE has a non-Crashlytics handler (mono_sigfpe_signal_handler).  This will interfere with reporting.
    
 [Crashlytics] The signal SIGILL has a non-Crashlytics handler (<redacted>).  This will interfere with reporting.
    
 [Crashlytics] The signal SIGSEGV has a non-Crashlytics handler (mono_sigsegv_signal_handler).  This will interfere with reporting.
    
 [Crashlytics] The signal SIGSYS has a non-Crashlytics handler (mono_crashing_signal_handler).  This will interfere with reporting.
 [Crashlytics] The signal SIGTRAP has a non-Crashlytics handler ((null)).  This will interfere with reporting.

I even get symbols uploaded successfully in the logs during build process in Visual Studio.

What I've tried

Tried uninstalling App Center Analytics. [I'm not using App Center Crashlytics]
Tried finding which is interfering with Crashlytics, don't have an idea how to find this..

Other Analytics SDKs I'm using

Google Analytics
Firebase Analytics


dotnet-xamarin
· 9
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

NOTE : I didn't have this problem before upgrade. Earlier Crashlytics version I was using : 3.14.0

0 Votes 0 ·

@Paul-9359 Did you add the Crashlytics.SharedInstance.Init(); line code? Someone faced the similar issue and solved it by adding this command. And I see you've reported this issue on github, please follow the topic to get the solution.


0 Votes 0 ·

Hi @JarvanZhang-MSFT ! yes, I have that initialization code

0 Votes 0 ·

Also, may I know why do Xamarin's GoogleApisForiOSComponents repo members don't respond to the issues opened in https://github.com/xamarin/GoogleApisForiOSComponents/issues. I can see this case in atleast all the recently opened issues in this repo..!

0 Votes 0 ·
Show more comments

@Paul-9359 Did you got the solution?

0 Votes 0 ·
Paul-9359 avatar image
0 Votes"
Paul-9359 answered Paul-9359 edited

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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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

0 Votes 0 ·
CorneliuSerediuc-8580 avatar image
0 Votes"
CorneliuSerediuc-8580 answered CorneliuSerediuc-8580 commented

We get the same thing after update:

[Crashlytics] The signal SIGABRT has a non-Crashlytics handler ((null)). This will interfere with reporting.
[Crashlytics] The signal SIGILL has a non-Crashlytics handler ((null)). This will interfere with reporting.
[Crashlytics] The signal SIGTRAP has a non-Crashlytics handler ((null)). This will interfere with reporting.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@CorneliuSerediuc-8580, was this issue fixed for you? I'm trying for a solution still..

0 Votes 0 ·

No, I have not!

1 Vote 1 ·