For more information and examples for how custom breadcrumbs can be integrated, see Customizing breadcrumbs. leaveBreadcrumb ( withMessage : "Button tapped" )īugsnag will keep track of the time and order of the breadcrumbs and show them on your dashboard.Īdditional data can also be attached to breadcrumbs by providing the optional type and metadata parameters. You can use the leaveBreadcrumb method to log potentially useful events in your own applications: For installation instructions, see our Customizing breadcrumbs guide. If your app makes network requests via URLSession, you can install the BugsnagNetworkRequestPlugin to capture network requests as breadcrumbs in your error reports. Automatically captured breadcrumbsīy default, BugSnag captures common events including: A configurable number of breadcrumbs are attached to each error report to help diagnose what events led to the error. In order to understand what happened in your application before each error, it can be helpful to leave short log statements that we call breadcrumbs. setUser ( "3", withEmail :, andName : "Bugs Nag" )įor more information, see Adding user data. If you would like to override this identifier you can set the user ID property. Bugsnag includes helpers for attaching an identifier, email address and name to reports that will be searchable in the dashboard.īy default we will generate a unique ID and send this ID along with every error report from an individual device. In order to correlate errors with customer reports, or to see a list of users who experienced each error, it is helpful to capture and display user information. start ( with : config )įor more information, see Customizing error reports. ( instancetype ) initWithCoder :( NSCoder * ) coder Bugsnag. If your app implements an app delegate, import the Bugsnag module and initialize Bugsnag in the application:didFinishLaunchingWithOptions: method: You can find your API key in Project Settings from your Bugsnag dashboard. Basic configurationĬonfigure your API key by adding a bugsnag Dictionary to your ist file: Under the General tab, click the Frameworks, Libraries and Embedded Content section’s + button and select amework (from ‘Bugsnag-iOS’). Select your project in the Project Navigator and in the project editor that appears, select your app’s target. Manual installationĬlone the Bugsnag GitHub repository: git clone ĭrag Bugsnag.xcodeproj into your Xcode workspace. Then run Carthage to generate the framework to add to your project: carthage update -use-xcframeworks -platform iosĭrag amework from Carthage/Build to your project. Using CarthageĪdd Bugsnag to your Cartfile: github "bugsnag/bugsnag-cocoa" Search for as the package URL, then click Add Package. Open your Xcode project and select File → Add Packages… Documentation for the previous release can be found on our legacy pages.Īdd the Bugsnag pod to your Podfile: pod 'Bugsnag'ĭon’t forget to run pod install after updating your Podfile. If you are using older versions, we recommend upgrading to the latest release using our Upgrade guide. This documentation is for version 6 of the BugSnag iOS notifier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |