LinkedIn Twitter YouTube
Features Competitive Analysis How It Works Frequently Asked Questions Getting Started Downloads
About News Store
Demo Software
Request Pricing

Testing the sample application 'MyCocoaCrasher'

Before you enable your Cocoa application with BugSplat technology, you may want to take a moment to examine the defect reports created with our sample application. To do this, login to BugSplat with user name 'Fred' and password 'Flintstone'. All the defect reports in the Fred account are actual crashes created with one of our sample applications. Defect reports from the application MyCocoaCrasher are mixed in with defect reports from Windows and Java applications. To view just the Cocoa application crashes you can filter on application name "MyCocoaCrasher" on the Custom Reports page.

Testing the sample application 'MyCocoaCrasher'

Mount the disk image (MyCocoaCrasher.dmg) that you just downloaded. Notice that it contains:

You will embed the BugSplat.Framework into your application.

Build the MyCocoaCrasher project and launch it without making any changes.

Each button on the dialog will cause a crash. When a crash occurs, fill out the requested information and select 'Send'. You can verify that crash report was created by logging into BugSplat with user 'Fred' and password 'Flintstone' and selecting 'All Crash Reports'.

Look for a recent crash post that has the crash description you created.

Modifying the sample application 'MyCocoaCrasher' to use your BugSplat account

Next, we will change the sample app so that crash reports are sent to your user id.
In MyCocoaCrasher.m search for the following line:

    [bugSplat initWithVendor:@"Fred" appName:@"MyCocoaCrasher" version:@"1.0"];

Make the following changes:

Build the MyCocoaCrasher project.

Next, launch MyCocoaCrasher and select a crash button.
Fill in the requested information in the crash dialog and select "Send Report"

   Crash Report

To verify that the report was sent, log into BugSplat and verify the defect was recorded.