Another crash reporter? Why?
Because all existing solutions fall short. PLCrashReporter comes very close, but not quite:
It can't handle stack overflow crashes.
It doesn't fill in all fields for its Apple crash reports.
It can't symbolicate on the device.
It only records enough information for an Apple crash report, though there is plenty of extra useful information to be gathered!
As well, each crash reporter service, though most of them use PLCrashReporter at the core, has its own format and API.
KSCrash is superior for the following reasons:
It catches ALL crashes.
Its pluggable server reporting architecture makes it easy to adapt to any API service (it already supports Hockey and Quincy and sending via email, with more to come!).
It supports symbolicating on the device.
It records more information about the system and crash than any other crash reporter.
It is the only crash reporter capable of creating a 100% complete Apple crash report (including thread/queue names).
It can be compiled with or without ARC.