We are getting a crash in send bird sdk.
Here is the crash stack trace:
Crashed: com.sendbird.SocketRocket.NetworkThreadCFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 24NSThread__start + 792
We are using following pods:
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
Woo
December 15, 2021, 1:01am
4
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
3 Likes
@Woo I’m also using 3.1.1 and still currently experience the crash
1 Like
Woo
January 4, 2022, 11:26pm
7
@hirophan @Joel_Alcantara could you guys send application id via DM? I will manaully turn on an application attribute to use native socket
fante
January 5, 2022, 12:32am
8
Hi @Woo i also experiencing the crash. Please check your DM
Woo
January 5, 2022, 1:13am
10
Let me investigate a bit more and get back to you guys! Thanks for your patient
Woo
January 5, 2022, 1:16am
11
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?
It was turned on. Our devs mention that this should stop gradually.
For the last 7 days, we still got more than 100 crashes
@hirophan Escalating this now to see more in detail what could be happening.
Hi guys, any update about this? I still got crashes
So, for @hirophan issue. Report shows that this build (4.8.3) is using Sendbird 3.1.2 and still reporting crashes.
Woo
February 9, 2022, 9:45am
21
If the server flag was previously false then whatever version a user uses, he/she could experience crash once at any given time even though current server flag is true. Because SDK retrieves this flag after initial connection with sendbird server, it uses legacy websocket framework for initial connection. But once it retrieves the flag, then it will no longer use legacy.
@hirophan do you see any users who experience the crash multiple times?
