#RBReporter

##Summary RBReporter is a facade to make it easy to receive error reports, notify users of errors, and log errors. RBReporter also includes support for Flurry Analytics. You only need to interact with RBReporter; however, you can still use the underlying classes if necessary.

##Dependencies RBReporter relies on some of my categories. Be sure to also include my UIWindow+RBExtras, UIViewController+RBExtras, NSString+RBExtras, NSURL+RBExtras, and NSDate+RBExtras. They can be found in my RBCategories repository.

RBReporter also depends on MessageUI.framework.

Flurry is an optional feature. To use the Flurry features you must include the Flurry SDK which can be found at Flurry.com.

RBReporter is written for iOS 4.0+ support. It can be modified for 3.0+ support by switching GCD with NSOperationQueue. RBReporter has not been written with the intent to work with the Mac platform. However, it can be easily extended. The only part that should be iOS-dependent is RBBugReportEmailBuilder. You can modify the email code to work with Mac. Alternatively, you could ignore emailing and simply send log files over the network, for example.

##Email

###Generating email reports One of the standard ways for a user to report bugs is through email. The RBEmailBuilder protocol provides a standard interface for generating email content. RBEmailBuilder uses a simple builder pattern (see Design Patterns: Elements of Reusable Object-Oriented Software or Wikipedia). RBBaseEmailBuilder provides a basic implementation of the RBEmailBuilder protocol which can be inherited by subclasses.

###Receiving email reports RBReporter provides a template email composer, but you can create your own email builders by creating a class that conforms to RBEmailBuilder. You can present the mail composer from anywhere in your code, incuding non-view controllers. Typically you want to prompt the user to report a bug or provide a button for sending reports (see example below).

// Prompt the user to report an error...

// Present the email composer.
RBBugReportEmailBuilder * builder [[RBBugReportEmailBuilder alloc] initWithError:error];
[RBReporter presentBugReportComposerWithBuilder:builder];
[builder release];

##User notifications RBReporter includes a convenience method for presenting simple messages to users. These messages are intended to present information or notify of errors where no immediate action is required. The following is an example:

[RBReporter presentAlertWithTitle:@"Testing" 
                          message:@"Testing simple message presentation."];

##Data Logging

###Logging errors Logging errors is made very easy. Just pass the error to RBReporter. Exceptions can be handled similarly.

NSError * error = nil;

// Some code that might generate an error.

if (error) {
	[RBReporter logError:error];
}

###RBLogger RBReporter provides a facade to the underlying logger; however, if you need to directly access the logger, you may. The logger is also designed to create a new log file every day. This keeps log files smaller and makes it easy to clean up old log files. Furthermore, the logger is designed to automatically purge old files if desired. Simply set kAutoPurgeLogFiles in RBLogger to YES and kDefaultLogFileAgeLimit to the number of days of log files to keep.

###RBLogFile RBLogFile provides an interface for the log files RBLogger uses. These files can direct their output to a file on the local file system or on a remote server. This also makes the format of the log file independent of the logger. RBExtendedLogFile is included for use as is or as a template for other log files. It uses a modification of the extended log file format. RBBaseLogFile provides a simple implementation and may be subclassed to define custom behavior.

###RBLogFileFactory RBLogger is intended to only use one type of log file. RBLogFileFactory is responsible for creating log files so RBLogger doesn't need to know anything about your own implementation of RBLogFile. By changing newLogFileWithPath: you can change the file format of your log files.

##Flurry In addition to standard reporting methods, RBReporter provides an optional facade to Flurry. Flurry reporting can also be disabled when debugging to prevent mixing debugging sessions with regular user sessions.

###Including Flurry

1. Include the Flurry SDK. See Flurry.com for details.

2. In the Xcode build settings, look for "Preprocessor Macros". Define the macro FLURRY for all build configurations.

3. (Optional) To disable Flurry reports when debugging, define the macro DEBUG for just the debug build configuration.

###Flurry reporting There are several simple methods for Flurry. RBReporter can log errors, exceptions, and events. The following gives examples of each.

// Simple error reporting.
[RBReporter sendFlurryReportWithError:error];

// Customized error reporting.
[RBReporter sendFlurryReportWithTitle:@"Error"
                              message:@"An error occurred"
                                error:error];

// Customized exception reporting.
[RBReporter sendFlurryReportWithTitle:@"Error"
                              message:@"An error occurred"
                            exception:exception];

// Simple event logging.
[RBReporter logFlurryEvent:anEventName];

##License

RBReporter is licensed under the MIT license, which is reproduced in its entirety here:

Copyright (c) 2011 Robert Brown

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.