To help investigate the cause of a crash, you can have Splunk MINT to report the flow of events a user experienced leading up to the crash. When you know this sequence of things the user did with your app before it crashed, you are better equipped to reproduce the crash and diagnose the problem. To tag the events or actions in your app, add breadcrumbs to your code. Splunk MINT retains data associated with a maximum of 16 breadcrumbs prior to a crash.
- Use the leaveBreadcrumb: method at the points of interest in your code as follows:
- Use the clearBreadcrumbs: method to clear the breadcrumb list as follows:
// Objective-C [[Mint sharedInstance] leaveBreadcrumb:@"InTheSettingsController"];
// Swift Mint.sharedInstance().leaveBreadcrumb("InTheSettingsController")
// Objective-C [[Mint sharedInstance] clearBreadcrumbs];
// Swift Mint.sharedInstance().clearBreadcrumbs()
To view breadcrumbs in a crash report, click an error on the Errors dashboard in Splunk MINT Management Console, and then click Breadcrumbs in the error detail area.
Add custom data to crash reports
This documentation applies to the following versions of Splunk MINT™ SDK for iOS (Legacy): 5.2.x