Crash at SBDCommandProcessor.m line 861

Hi sendbird team

we have about 1000 crash record on firebase recently after we update the SDK to v3.0.226
it didn’t crash before and we didn’t change any app side source code. so we guess it’s root cause is
inside the sendbird iOS sdk. currently we update to the latest v3.0.231 and keep monitoring the crash logs.

here is the crash log we get from firebase crashlytics.
hoping it can help:

Fatal Exception: NSInvalidArgumentException
0 CoreFoundation 0x186465754 __exceptionPreprocess
1 libobjc.A.dylib 0x19af2c7a8 objc_exception_throw
2 CoreFoundation 0x1864d7a18 -[__NSCFString characterAtIndex:].cold.1
3 CoreFoundation 0x1864d5444 -[__NSPlaceholderArray initWithCapacity:].cold.1
4 CoreFoundation 0x186346a10 -[__NSPlaceholderArray initWithObjects:count:]
5 CoreFoundation 0x1863414c4 +[NSArray arrayWithObjects:count:]
6 SendBirdSDK 0x1044c3bb0 __51-[SBDCommandProcessor processChannelEvent:isEnter:]_block_invoke_2 + 861 (SBDCommandProcessor.m:861)
7 SendBirdSDK 0x1044c8a80 __54+[SBDOpenChannel getChannelWithUrl:completionHandler:]_block_invoke + 318 (SBDOpenChannel.m:318)
8 SendBirdSDK 0x1044c8d74 __69+[SBDOpenChannel getChannelWithUrl:apiRequestType:completionHandler:]_block_invoke_2 + 338 (SBDOpenChannel.m:338)
9 libdispatch.dylib 0x186050a84 _dispatch_call_block_and_release
10 libdispatch.dylib 0x18605281c _dispatch_client_callout
11 libdispatch.dylib 0x186060c70 _dispatch_main_queue_callback_4CF
13 CoreFoundation 0x1863d9270 __CFRunLoopRun
14 CoreFoundation 0x1863d8360 CFRunLoopRunSpecific
15 GraphicsServices 0x19da16734 GSEventRunModal
16 UIKitCore 0x188e53584 -[UIApplication _run]
17 UIKitCore 0x188e58df4 UIApplicationMain
18 NBA Rakuten 0x102fcc318 main + 23 (PlayerCollectionCell.swift:23)
19 libdyld.dylib 0x186094cf8 start

I will look into what’s root cause on this issue. Thanks for reporting it @yuli.sun

I think latest version will not cause this issue. it has been patched.

1 Like

We had updated to latest v3.0.231
and will continues monitoring the crash log
Thanks, I will report here if it no more crash using v3.0.231

we never reproduced the crash, it only recorded on firebase crashlytics
so it will take times until we finally confirmed