iOS Question How to understand the crash report from KSCrash?

Sandman

Expert
Licensed User
I've implemented support for KSCrash in my app, and have received my first crash report. I'm not sure how to understand the information in it though.

What am I supposed to do with it? Sure, I get a clue to where the problem is, but I can't parse the report well enough to really to pinpoint the problem. Am I supposed to understand something detailed in it? Or am I supposed to open it in XCode somehow and it helps me understand it?

This is the part of the report that I believe is relevant:
B4X:
-- headers removed --

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000 at 0x0000000000000000
Crashed Thread:  0

Application Specific Information:
*** Terminating app due to uncaught exception '', reason: 'Cannot parse: '

Thread 0 Crashed:
0   CoreFoundation                  0x0000000185991dc0 0x185868000 + 1220032
1   libobjc.A.dylib                 0x000000019a4ee7a8 objc_exception_throw + 60
2   CoreFoundation                  0x0000000185886e74 0x185868000 + 126580
3   MyAwesomeApp                    0x00000001049d6388 -[B4I ObjectToNumber:] + 360
4   MyAwesomeApp                    0x00000001049637a0 -[ResumableSub_cl_geofence_AddGeofence resume::] + 1160
5   MyAwesomeApp                    0x0000000104965a00 -[b4i_cl_geofence _addgeofence:] + 156
6   MyAwesomeApp                    0x0000000104977724 -[ResumableSub_cl_punchclock_punchin resume::] + 2848
7   MyAwesomeApp                    0x00000001049d54d0 -[B4I checkAndRunWaitForEvent:event:params:] + 428
8   MyAwesomeApp                    0x00000001049d5204 -[B4I raiseEvent:event:params:] + 284
9   MyAwesomeApp                    0x00000001049dd08c __37-[B4ICommon ReturnFromResumableSub::]_block_invoke + 264
10  libdispatch.dylib               0x000000018557ca84 0x18557a000 + 10884
11  libdispatch.dylib               0x000000018557e81c 0x18557a000 + 18460
12  libdispatch.dylib               0x000000018558cc70 _dispatch_main_queue_callback_4CF + 884
13  CoreFoundation                  0x000000018590ba2c 0x185868000 + 670252
14  CoreFoundation                  0x0000000185905904 0x185868000 + 645380
15  CoreFoundation                  0x00000001859049f4 CFRunLoopRunSpecific + 600
16  GraphicsServices                0x000000019cfda734 GSEventRunModal + 164
17  UIKitCore                       0x000000018838375c 0x1877b9000 + 12363612
18  UIKitCore                       0x0000000188388fcc UIApplicationMain + 168
19  MyAwesomeApp                    0x00000001048ddb78 main + 104
20  libdyld.dylib                   0x00000001855c0cf8 0x1855bf000 + 7416

-- lots of info about threads and binary images removed --

Extra Information:

Notable Addresses:
{}

Application Stats:
{
    "active_time_since_last_crash": 21.7899,
    "active_time_since_launch": 21.7899,
    "application_active": true,
    "application_in_foreground": true,
    "background_time_since_last_crash": 0,
    "background_time_since_launch": 0,
    "launches_since_last_crash": 1,
    "sessions_since_last_crash": 1,
    "sessions_since_launch": 1
}

CrashDoctor Diagnosis: Application threw exception : Cannot parse:
Originated at or in a subcall of -[B4I ObjectToNumber:]

Yes, I do see the problem with me apparently trying to parse an object as a number, but I've looked in the subs mentioned and I can not find where I would be doing that.

Also: Most lines in the crash end with a plus and a number. Does that mean something relevant? Example:
B4X:
4   MyAwesomeApp                    0x00000001049637a0 -[ResumableSub_cl_geofence_AddGeofence resume::] + 1160
 
Top