Crash on IOS Couchbase lite

Hi ,
i am using couchbase lite in my IOS application i got this kind of exception in my Crashlytics log .i Can Not even find out at what and which point it is making a crash. can you give some idea regarding this .

please help me out , thanks in advance .

my log is

Crashed: CouchbaseLite
0 InteractiveContacts2 0x1001e9238 CLSProcessRecordAllThreads + 4296823352
1 InteractiveContacts2 0x1001e9238 CLSProcessRecordAllThreads + 4296823352
2 InteractiveContacts2 0x1001e9658 CLSProcessRecordAllThreads + 4296824408
3 InteractiveContacts2 0x1001da318 CLSHandler + 4296762136
4 InteractiveContacts2 0x1001e794c __CLSExceptionRecord_block_invoke + 4296816972
5 libdispatch.dylib 0x183a8947c _dispatch_client_callout + 16
6 libdispatch.dylib 0x183a94728 _dispatch_barrier_sync_f_invoke + 100
7 InteractiveContacts2 0x1001e73f8 CLSExceptionRecord + 4296815608
8 InteractiveContacts2 0x1001e7234 CLSExceptionRecordNSException + 4296815156
9 InteractiveContacts2 0x1001e6e94 CLSTerminateHandler() + 4296814228
10 libc++abi.dylib 0x183696f44 std::__terminate(void ()()) + 16
11 libc++abi.dylib 0x18369685c __cxxabiv1::exception_cleanup_func(_Unwind_Reason_Code, _Unwind_Exception
) + 134
12 libobjc.A.dylib 0x1836a4094 _objc_exception_destructor(void*) + 330
13 CoreFoundation 0x18403ec80 +[NSException raise:format:] + 106
14 Foundation 0x1849c41c0 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 88
15 InteractiveContacts2 0x100274ec4 _AssertFailed + 4297395908
16 InteractiveContacts2 0x10026ba5c CBLGeoJSONBoundingBox + 4297357916
17 InteractiveContacts2 0x10023393c CBLStemmerNameForCurrentLocale + 4297128252
18 InteractiveContacts2 0x10026b7f0 CBLGeoJSONBoundingBox + 4297357296
19 CFNetwork 0x1847b96a0 __65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke + 80
20 CFNetwork 0x1847b9630 -[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:] + 200
21 CFNetwork 0x1847b97a4 -[NSURLConnectionInternal _withActiveConnectionAndDelegate:] + 56
22 CFNetwork 0x18478ce84 _NSURLConnectionDidReceiveData(_CFURLConnection*, __CFData const*, long, void const*) + 76
23 CFNetwork 0x18461c7d8 ___ZN27URLConnectionClient_Classic29_delegate_didReceiveDataArrayEv_block_invoke + 232
24 CFNetwork 0x18471341c ___ZN27URLConnectionClient_Classic18_withDelegateAsyncEPKcU13block_pointerFvP16_CFURLConnectionPK33CFURLConnectionClientCurrent_VMaxE_block_invoke_2 + 108
25 libdispatch.dylib 0x183a8947c _dispatch_client_callout + 16
26 libdispatch.dylib 0x183a927b8 _dispatch_block_invoke + 540
27 CFNetwork 0x18460bac0 RunloopBlockContext::_invoke_block(void const*, void*) + 36
28 CoreFoundation 0x183f1c67c CFArrayApplyFunction + 68
29 CFNetwork 0x18460b9a4 RunloopBlockContext::perform() + 136
30 CFNetwork 0x18460b864 MultiplexerSource::perform() + 312
31 CFNetwork 0x18460b690 MultiplexerSource::_perform(void*) + 68
32 CoreFoundation 0x183ff509c CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 24
33 CoreFoundation 0x183ff4b30 __CFRunLoopDoSources0 + 540
34 CoreFoundation 0x183ff2830 __CFRunLoopRun + 724
35 CoreFoundation 0x183f1cc50 CFRunLoopRunSpecific + 384
36 Foundation 0x18492ccfc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 308
37 InteractiveContacts2 0x1002172ec CBLCompareRevIDs + 4297011948
38 Foundation 0x184a13e4c NSThread__start + 1000
39 libsystem_pthread.dylib 0x183ca3b28 _pthread_body + 156
40 libsystem_pthread.dylib 0x183ca3a8c _pthread_body + 154
41 libsystem_pthread.dylib 0x183ca1028 thread_start + 4

Unfortunately debug symbols aren’t available for your app, so the symbol names shown in the backtrace aren’t useful; the crash logger just shows the nearest symbol it knows about, no matter how far away it is. You can tell this is going on when the offsets (like +4296823352) are crazy huge numbers.

Without knowing what methods/functions are really involved, there’s no way to diagnose this.

If you’re using Couchbase Lite 1.2 or 1.2.1, the library we built was missing symbols, so this could be the cause. I suggest upgrading to 1.3. If you’re already on 1.3, the problem is probably that your app was built without symbols, or that you haven’t provided Crashlytics with the dSYM file for them to decipher the crash logs.