Consider the backtrace you got:
Application Specific Backtrace 0:
0 CoreFoundation … __exceptionPreprocess + 242
1 libobjc.A.dylib … objc_exception_throw + 48
2 CoreFoundation … -[NSObject(NSObject) __retain_OA] + 0
3 CoreFoundation … ___forwarding___ + 742
4 CoreFoundation … _CF_forwarding_prep_0 + 120
5 ********** … ********** + 1118297
6 CoreFoundation … __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 137
7 CoreFoundation … ___CFXRegistrationPost_block_invoke + 88
8 CoreFoundation … _CFXRegistrationPost + 536
9 CoreFoundation … _CFXNotificationPost + 735
10 Foundation … -[NSNotificationCenter postNotificationName:object:userInfo:] + 82
11 ********** … ********** + 1120924
12 ********** … ********** + 170626
13 libdispatch.dylib … _dispatch_call_block_and_release + 12
Frame 13 indicates that your code was called by Dispatch. Frames 12 through 10 show it posting a notification. Frames 11 through 6 are notification machinery, which eventually calls your notification handler in from 5. This has done something weird, which has triggered a language exception.
It’s hard to say exactly what the weird thing is but the next step is clear: Symbolicate your log to uncover the identities of the code in frames 12, 11, and 5. For advice on how to do that, see Adding Identifiable Symbol Names to a Crash Report.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"