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

Question

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

Answer 1

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.

Answer 2

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.