Thanks for the crash report. This part of the report:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0xbed59ae800000001
indicates that the app crashed because it’s accessing an invalid pointer, one that doesn’t point to mapped memory. And indeed that pointer looks really weird, being way up in high memory.
And here’s the backtrace of the crashing thread:
Thread 0 Crashed:
0 libsystem_platform.dylib … _platform_strcmp + 8
1 eBook … 0x100b50000 + 5833168
2 eBook … 0x100b50000 + 5833432
3 libobjc.A.dylib … call_load_methods + 184
Frame 3 indicates that the Objective-C runtime is calling a
method on some class. Frames 2 through 1 are your code, and they’re not symbolicated so it’s hard to say what’s going on. Frame 0 indicates that your code called
, which is what crashed.
will only crash if you pass it bogus parameters, so you need to investigate why your app has done that.
The next step here is to symbolicate your crash report to uncover the identity of frames 2 through 1. Technote 2151 Understanding and Analyzing iOS Application Crash Reports has info on symbolication.
Share and Enjoy
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"