When an unhandled fault is detected, Objective-See apps, kindly generate various error information that is logged to the system log. For example, it provided the reason for the crash as well as the instruction/call stack where the crash occurred. In many cases, this information can pinpoint the exact location of the bug, making it easy to found and fix! Recently Apple made changes to their logging mechanisms, which resulted in a change to how this valuable crash data is stored. Below are instrunctions for versions of OS X prior to Sierra, and then for Sierra (and above).
Mac OS X (pre-macOS Sierra)
On OS X, one can view crash information via the Console application (/Applications/Utilities/Console.app). Once you've opened the Console, find the app's error information by typing OBJECTIVE-SEE in the filter/search field. Copy and paste this error information into an email and I'll try my best to track down the bug and fix it right away :)
In macOS Sierra, Apple introduced new logging mechanisms, meaning the crash data may have to be retrieved in a new manner. First, (as described above), try search via the Console application (making sure to select your computer name under 'Devices' in the log list). If nothing shows up there, try the following method.
Open the Terminal application (/Applications/Utilities/Terminal.app). Then type (or cut and paste) the following command:
log show --predicate 'eventMessage contains "OBJECTIVE-SEE ERROR"' --info
Hit enter, and then wait (a bit) until the command completes:
$ log show --predicate 'eventMessage contains "OBJECTIVE-SEE ERROR"' --info
2017-03-17 10:16:44.575047-1000 0x762cc7 Default 0x0 32817 KnockKnock: OBJECTIVE-SEE ERROR: OS version: Version 10.12.3 (Build 16D32) /App version: 1.9.0
2017-03-17 10:16:44.575102-1000 0x762cc7 Default 0x0 32817 KnockKnock: OBJECTIVE-SEE ERROR: unhandled obj-c exception caught [name: NSInternalInconsistencyException / reason: Invalid parameter not satisfying: aString != nil]
2017-03-17 10:16:44.579553-1000 0x762cc7 Default 0x0 32817 KnockKnock: OBJECTIVE-SEE ERROR: (
0 KnockKnock 0x0000000108167ca8 exceptionHandler + 472
1 CoreFoundation 0x00007fffa2f42d89 __handleUncaughtException + 745
2 libobjc.A.dylib 0x00007fffb7b58b85 _ZL15_objc_terminatev + 94
3 libc++abi.dylib 0x00007fffb704bd69 _ZSt11__terminatePFvvE + 8
4 libc++abi.dylib 0x00007fffb704bde3 _ZSt9terminatev + 51
5 libdispatch.dylib 0x00007fffb84020cc _dispatch_client_callout + 28
6 libdispatch.dylib 0x00007fffb840f068 _dispatch_barrier_sync_f_slow_invoke + 295
7 libdispatch.dylib 0x00007fffb84020b8 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fffb840fb4b _dispatch_main_queue_callback_4CF + 925
9 CoreFoundation 0x00007fffa2e7b669 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
10 CoreFoundation 0x00007fffa2e3c65d __CFRunLoopRun + 2221
Again, if you email this crash data to firstname.lastname@example.org I'll try my best to track down and fix the bug, ASAP!