CODEWITHSUNDEEP
ios
Wingzero
Wingzero

Reputation: 9754

crashlytics don't detect crash file to submit, affected by Umeng SDK

I setup crashlytics and turning on debug mode,

I tried [[Crashlytics sharedInstance] crash]; it will have files to submit;

I tried int *x = NULL; *x = 42; it will have files to submit;

But I tried 

NSArray *a = @[@1,@2];
[a objectAtIndex:5];

it will not have files to submit. What is the condition for crashlytics to generate files to submit? I am confused it seems not every crash it will report.

The [a objectAtIndex:5]; log:

2015-02-13 13:34:11.344 Compass[1589:277586] [Crashlytics] Settings loaded
2015-02-13 13:34:11.351 Compass[1589:277586] [Crashlytics] Configuring application
2015-02-13 13:34:11.352 Compass[1589:277586] [Crashlytics] Starting report processing in 1.0 second(s)...
2015-02-13 13:34:12.451 Compass[1589:277587] [Crashlytics] Alternate file submission complete
2015-02-13 13:34:12.453 Compass[1589:277587] [Crashlytics] No prepared files found
2015-02-13 13:34:12.454 Compass[1589:277587] [Crashlytics] No sendable files, submission process complete
2015-02-13 13:34:13.272 Compass[1589:277585] [Crashlytics] Configured application

compared to [[Crashlytics sharedInstance] crash]:

2015-02-13 15:36:11.716 Compass[1634:288568] [Crashlytics] Processed file successfully
2015-02-13 15:36:11.717 Compass[1634:288568] [Crashlytics] Alternate file submission complete
2015-02-13 15:36:11.718 Compass[1634:288568] [Crashlytics] Submitting files
2015-02-13 15:36:13.750 Compass[1634:288561] [Crashlytics] Submission response: {status: 202, error: (null)}
2015-02-13 15:36:13.751 Compass[1634:288561] [Crashlytics] Submitted crash report with file name: "54dda95f01cf0001065d333333376237.cls", request-id: <none received>
2015-02-13 15:36:13.752 Compass[1634:288569] [Crashlytics] Submitted file successfully
2015-02-13 15:36:13.754 Compass[1634:288569] [Crashlytics] No sendable files, submission process complete

Upvotes: 0

Views: 421

Answers (1)

Wingzero
Wingzero

Reputation: 9754

Self answer:

It turned out to be that another SDK called Umeng also has a crash reporting feature, and it silently handled all exceptions, so I suppose crashlytics cannot get the exception.

I did disabled Umeng SDK crash reporting, but the true magic is:

[MobClick setCrashReportEnabled:NO];
[MobClick startWithAppkey:@"Your Key"];

[MobClick setCrashReportEnabled:NO]; must put before startWithAppkey:, otherwise it is already set.

I am delighted by Crashlytics don’t send crash report when there is another crash report (Umeng)

Upvotes: 2

Related Questions