Interference with Crashlytics

[Usipov]

Hello!
Disabled debug executable flag in the scheme and launched the app. Got these logs:

16:40:33:657 YandexMobileMetrica: Activated. Version:2.80, Release build 7224
[Crashlytics] The signal SIGABRT has a non-Crashlytics handler (PodYandexMobileMetrica_kssighndl_i_handleSignal).  This will interfere with reporting.
[Crashlytics] The signal SIGBUS has a non-Crashlytics handler (PodYandexMobileMetrica_kssighndl_i_handleSignal).  This will interfere with reporting.
[Crashlytics] The signal SIGFPE has a non-Crashlytics handler (PodYandexMobileMetrica_kssighndl_i_handleSignal).  This will interfere with reporting.
[Crashlytics] The signal SIGILL has a non-Crashlytics handler (PodYandexMobileMetrica_kssighndl_i_handleSignal).  This will interfere with reporting.
[Crashlytics] The signal SIGSEGV has a non-Crashlytics handler (PodYandexMobileMetrica_kssighndl_i_handleSignal).  This will interfere with reporting.
[Crashlytics] The signal SIGSYS has a non-Crashlytics handler (PodYandexMobileMetrica_kssighndl_i_handleSignal).  This will interfere with reporting.
[Crashlytics] The signal SIGTRAP has a non-Crashlytics handler (PodYandexMobileMetrica_kssighndl_i_handleSignal).  This will interfere with reporting.

Is that ok? Looks strange

[bamx23]

AppMetrica has its own crashes handling that can partially conflict with other crash reporting systems.

[Usipov]

Can AppMetrica's crash reporting be disabled?

[Usipov]

We call

[YMMYandexMetrica setReportCrashesEnabled:NO];

However, it looks like intereference takes place anyway

[bamx23]

Yes, we're going to allow disabling of crash handling in further releases.
Is there any problem with two crash handlers for you?

[Usipov]

I do not know whether you invoke previous singlal handlers or previous uncaught exception handlers.
Looks like Crashlytics works as expected.
Just wanted to report the issue.