• Home
• Solution
• Company
• Contact

Getting Started with Mac OS X Cocoa Applications

On this page, we will show you in a few simple steps how your Cocoa application can be modified to provide full debug information on the BugSplat website when it crashes. To get a feel for the BugSplat service prior to enabling your application, feel free to experiment with the MyCocoaCrasher sample application which is part of the BugSplat software development kit that can be downloaded by registered users.

Enabling your application with BugSplat technology:

First, make sure you have completed the following checklist:

1. Register a BugSplat User Id for your company or group.
2. Download and unzip the BugSplat software development kit for Mac OS X Cocoa Applications.

Creating defect reports using your own application

Add BugSplat to your application as follows:

• Add the BugSplat.Framework to your Cocoa project.
• Add a Copy Files build step to the Targets to embed the framework onto your application.
• Import the BugSplat exception handler class: #import <BugSplat/BugSplat.h>.
• Add BugSplat member to the interface for your application class: BugSplat* bugSplat;.
• In the init method for your class, send the bugSplat object an initWithVendor message as shown in the sample code above for MyCocoaCrasher.
• Optionally, use these methods to set options:
  • setDescription - a description of your application
  • addAdditionalFiles - add a log file, system info, etc.
  • setQuietMode - suppress all dialogs (for server applications)

Remember to test your application by forcing a crash, and verify that crashes are posted and a good call stack is created.

Please contact us at support@bugsplatsoftware.com with any questions or problems you have - we want to help!