com.sendbird.SocketRocket.NetworkThread Crash

We are getting a crash in send bird sdk.

Here is the crash stack trace:

Crashed: com.sendbird.SocketRocket.NetworkThread
0 libobjc.A.dylib 0x2430 objc_release + 16
1 Foundation 0x43a90 -[_NSThreadPerformInfo dealloc] + 44
2 Foundation 0x3bdf4 __NSThreadPerformPerform + 192
4 CoreFoundation 0xc2238 __CFRunLoopDoSource0 + 204
5 CoreFoundation 0x55d8 __CFRunLoopDoSources0 + 256
6 CoreFoundation 0xaa08 __CFRunLoopRun + 768
7 CoreFoundation 0x1dd7c CFRunLoopRunSpecific + 572
8 Foundation 0x1800c -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 232
9 SendBirdSDK 0xc3068 -[SendBird_SRRunLoopThread main] + 70 (SendBird_SRRunLoopThread.m:70)
10 Foundation 0x64efc NSThread__start + 792
11 libsystem_pthread.dylib 0x63a4 _pthread_start + 116
12 libsystem_pthread.dylib 0x49fc thread_start + 8

We are using following pods:
pod ‘SendBirdDesk’, ‘1.0.8’
pod ‘SendBirdSDK’, ‘3.0.218’

1 Like

Hey guys, any update on this please?

I too have been facing this issue for last few days. My stack trace is:

Crashed: com.sendbird.SocketRocket.NetworkThread
0  libobjc.A.dylib                0x2bf0 objc_release + 16
1  Foundation                     0x458cc -[_NSThreadPerformInfo dealloc] + 48
2  Foundation                     0x3d3e4 __NSThreadPerformPerform + 240
3  CoreFoundation                 0xbb020 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
4  CoreFoundation                 0xcbce0 __CFRunLoopDoSource0 + 208
5  CoreFoundation                 0x5fe8 __CFRunLoopDoSources0 + 268
6  CoreFoundation                 0xb7f4 __CFRunLoopRun + 820
7  CoreFoundation                 0x1f3b8 CFRunLoopRunSpecific + 600
8  Foundation                     0x18354 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 236
9  SendBirdSDK                    0x639b8 -[SendBird_SRRunLoopThread main] + 70 (SendBird_SRRunLoopThread.m:70)
10 Foundation                     0x6836c __NSThread__start__ + 808
11 libsystem_pthread.dylib        0x19a4 _pthread_start + 148
12 libsystem_pthread.dylib        0xea0 thread_start + 8

Hello @Imran_jutt @chauhan130 we have known the issue and are working on to fix the problem. To fix this problem there are two steps, first is update SDK to latest (or 3.0.235 later) and secondly we need to configure application attribute internally.

Would you please first update sdk?

1 Like

I’m using the latest version 3.1.1 and got that crash too


@Woo I’m also using 3.1.1 and still currently experience the crash

1 Like

@hirophan @Joel_Alcantara could you guys send application id via DM? I will manaully turn on an application attribute to use native socket

Hi @Woo i also experiencing the crash. Please check your DM

Let me investigate a bit more and get back to you guys! Thanks for your patient

FYI, for those who uses SDK version lower than 3.0.226, please update your SDK.

Otherwise, if you are using latest (or at least 3.0.226) SDK and still experiencing this crash, please DM me your application id.

Someone from your company helped to turn it on, I will track and see if it happens again, thank you

I turned it on. Please test it again.

After you guys helped to turn it on, our app still got those crashes

Hi @hirophan Can you please DM me your application ID?
I can check if it was enabled.

It was turned on. Our devs mention that this should stop gradually.