问题:

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'

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

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?

回答1:

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];

转载请标明出处:Crashlytics don’t send crash report when there is another crash report (Umeng)

文章来源: Crashlytics don’t send crash report when there is another crash report (Umeng)

标签

crashlytics