Splunk MINT SDK for iOS

Splunk MINT SDK for iOS Developer Guide

Download manual as PDF

Download topic as PDF

Add breadcrumbs to crash reports

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:
  • // Objective-C
    [[Mint sharedInstance] leaveBreadcrumb:@"InTheSettingsController"];
    
    // Swift 
    Mint.sharedInstance().leaveBreadcrumb("InTheSettingsController")
    
  • Use the clearBreadcrumbs: method to clear the breadcrumb list as follows:
  • // 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.

PREVIOUS
Add custom data to crash reports
  NEXT
Track views

This documentation applies to the following versions of Splunk MINT SDK for iOS: 5.2.x


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters