当另一个崩溃报告（Umeng）时，Crashlytics不会发送崩溃报告 [英] Crashlytics don’t send crash report when there is another crash report (Umeng)

问题描述

我在我的iOS应用程序中实现了Crashlytics（2.2.4）以收集崩溃报告。我还为其他数据收集实现了另一个第三方组件（Umeng）。但是，当Umeng打开时，Crashlytics不会发送报告。当我检查日志时，会出现以下可疑警告：

I’ve implemented Crashlytics (2.2.4) in my iOS app for crash report collection. I also implemented another third-party component (Umeng) for other data collection. However, Crashlytics doesn’t send report when Umeng is turned on. When I check the log, there are these suspicious warnings:

[Crashlytics] Warning: NSUncaughtExceptionHandler is 'UmengHandleException'  
[Crashlytics] Warning: sigabrt handler is ‘UmengSignalHandler'  
[Crashlytics] Warning: sigbus handler is 'UmengSignalHandler' 
[Crashlytics] Warning: sigfpe handler is 'UmengSignalHandler' 
[Crashlytics] Warning: sigill handler is 'UmengSignalHandler' 
[Crashlytics] Warning: sigsegv handler is ‘UmengSignalHandler'

当Umeng关闭时，这些警告消失了，报告也很好发送。

When Umeng is turned off, these warnings are gone and the reports are well sent.

我已经把Crashlytics放在AppDelegate的最后一次调用，但警告仍在那里。
有没有办法解决这个问题，以便Crashlytics可以在Umeng打开时发送报告？

I have put Crashlytics last to call in AppDelegate, but the warning is still there. Is there a way to work around this issue so that Crashlytics can send report when Umeng is turned on?

推荐答案

自我回答。
我在Umeng的支持论坛上得到了另一位开发人员的建议，即在startWithKey方法之前设置报告禁用方法。诀窍是在不使用startWithKey之后使用此方法。我被这个pitfalll困了两天。

Self answer. I got an advice from another developer on Umeng's support forum, which is to put the set report disable method before the startWithKey method. The trick is to use this method BEFORE not after the startWithKey. I am trapped by this pitfalll for two days.

[MobClick setCrashReportEnabled:NO];
[MobClick startWithAppkey:YOURKEY reportPolicy:YOURPOLICY channelId:YOURCHANNELID];

这篇关于当另一个崩溃报告（Umeng）时，Crashlytics不会发送崩溃报告的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！