High crash rate with latest SDK

We recently updated the Meeting SDK for iOS from the previous version to version 6.1.5.16935. We are seeing a very high rate of crashes related to the following:

We aren’t able to recreate it, we just have reports from Xcode. I’m including details from the crash report.

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Reason: *** -[__NSArrayM objectAtIndex:]: index 266 beyond bounds [0 … 265]
Termination Reason: SIGNAL 6 Abort trap: 6
Terminating Process: Participant [1557]

Triggered by Thread: 0

Last Exception Backtrace:
0 CoreFoundation 0x19c458f20 __exceptionPreprocess + 164 (NSException.m:249)
1 libobjc.A.dylib 0x194306018 objc_exception_throw + 60 (objc-exception.mm:356)
2 CoreFoundation 0x19c3fa298 -[__NSArrayM objectAtIndex:] + 592 (NSArrayM.m:0)
3 MobileRTC 0x10b70ab4c 0x10b684000 + 551756
4 Foundation 0x19b2e9d60 -[NSString enumerateSubstringsInRange:options:usingBlock:] + 1592 (NSString.m:1422)
5 MobileRTC 0x10b70aa74 0x10b684000 + 551540
6 MobileRTC 0x10b70a8c4 0x10b684000 + 551108
7 Participant 0x104268c9c Audience.sendMessage(:to:) + 316 (Audience.swift:1116)
8 Participant 0x1042776b4 ChatViewController.sendMessage() + 880 (ChatViewController.swift:419)
9 Participant 0x104277288 ChatViewController.sendMessageTapped(
:slight_smile: + 4 (ChatViewController.swift:390)
10 Participant 0x104277288 @objc ChatViewController.sendMessageTapped(_:slight_smile: + 68 (:389)
11 UIKitCore 0x19ea5131c -[UIApplication sendAction:to:from:forEvent:] + 100 (UIApplication.m:5616)
12 UIKitCore 0x19ea511f4 -[UIControl sendAction:to:forEvent:] + 112 (UIControl.m:920)
13 UIKitCore 0x19ea51044 -[UIControl _sendActionsForEvents:withEvent:] + 324 (UIControl.m:991)
14 UIKitCore 0x19ef68080 -[UIButton _sendActionsForEvents:withEvent:] + 124 (UIButton.m:4173)
15 UIKitCore 0x19ef69894 -[UIControl touchesEnded:withEvent:] + 400 (UIControl.m:670)
16 UIKitCore 0x19e6e0e14 _UIGestureEnvironmentUpdate + 5796 (UIGestureEnvironment.m:214)
17 CoreFoundation 0x19c3f9658 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 36 (CFRunLoop.c:1789)
18 CoreFoundation 0x19c3f9414 __CFRunLoopDoObservers + 552 (CFRunLoop.c:1902)
19 CoreFoundation 0x19c42854c __CFRunLoopRun + 1028 (CFRunLoop.c:2983)
20 CoreFoundation 0x19c427cd8 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420)
21 GraphicsServices 0x1e12d81a8 GSEventRunModal + 164 (GSEvent.c:2196)
22 UIKitCore 0x19ea6090c -[UIApplication _run] + 888 (UIApplication.m:3713)
23 UIKitCore 0x19eb149d0 UIApplicationMain + 340 (UIApplication.m:5303)
24 Participant 0x104228874 main + 64 (AppDelegate.swift:16)
25 dyld 0x1bfad9e4c start + 2240 (dyldMain.cpp:1298)

The line Audience.swift:1116 is where we call the build function of MobileRTCMeetingChatBuilder. Again, this seemingly worked without issues in the previous version of the SDK.

Sometimes the stack trace does not contain anything from our code like this:

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Reason: *** -[__NSArrayM objectAtIndex:]: index 115 beyond bounds [0 … 114]
Termination Reason: SIGNAL 6 Abort trap: 6
Terminating Process: Participant [575]

Triggered by Thread: 0

Last Exception Backtrace:
0 CoreFoundation 0x191bbcf20 __exceptionPreprocess + 164 (NSException.m:249)
1 libobjc.A.dylib 0x189aca018 objc_exception_throw + 60 (objc-exception.mm:356)
2 CoreFoundation 0x191b5e298 -[__NSArrayM objectAtIndex:] + 592 (NSArrayM.m:0)
3 MobileRTC 0x1099d6b4c 0x109950000 + 551756
4 Foundation 0x190a4dd60 -[NSString enumerateSubstringsInRange:options:usingBlock:] + 1592 (NSString.m:1422)
5 MobileRTC 0x1099d6a74 0x109950000 + 551540
6 MobileRTC 0x10998204c 0x109950000 + 204876
7 MobileRTC 0x10998136c 0x109950000 + 201580
8 MobileRTC 0x1099b8f0c 0x109950000 + 429836
9 MobileRTC 0x10ad938d4 0x109950000 + 21248212
10 MobileRTC 0x10ae66c28 0x109950000 + 22113320
11 MobileRTC 0x109f2d234 0x109950000 + 6148660
12 MobileRTC 0x10a069a7c 0x109950000 + 7445116
13 MobileRTC 0x10a06d1f4 0x109950000 + 7459316
14 MobileRTC 0x109e93018 0x109950000 + 5517336
15 MobileRTC 0x10d15a930 0x109950000 + 58763568
16 MobileRTC 0x10d14ecd0 0x109950000 + 58715344
17 MobileRTC 0x10d132080 0x109950000 + 58597504
18 MobileRTC 0x109d53338 0x109950000 + 4207416
19 MobileRTC 0x109f160f0 0x109950000 + 6054128
20 MobileRTC 0x109f16398 0x109950000 + 6054808
21 MobileRTC 0x10bf6e658 0x109950000 + 39970392
22 MobileRTC 0x10bedd9a8 0x109950000 + 39377320
23 MobileRTC 0x10b892cd8 0x109950000 + 32779480
24 MobileRTC 0x10b892bc8 0x109950000 + 32779208
25 Foundation 0x190b99f1c __NSFireTimer + 96 (NSTimer.m:280)
26 CoreFoundation 0x191bf0a2c CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 32 (CFRunLoop.c:1797)
27 CoreFoundation 0x191bf06d0 __CFRunLoopDoTimer + 1004 (CFRunLoop.c:2404)
28 CoreFoundation 0x191bf022c __CFRunLoopDoTimers + 288 (CFRunLoop.c:2562)
29 CoreFoundation 0x191b8c888 __CFRunLoopRun + 1856 (CFRunLoop.c:3122)
30 CoreFoundation 0x191b8bcd8 CFRunLoopRunSpecific + 608 (CFRunLoop.c:3420)
31 GraphicsServices 0x1d6a3c1a8 GSEventRunModal + 164 (GSEvent.c:2196)
32 UIKitCore 0x1941c490c -[UIApplication _run] + 888 (UIApplication.m:3713)
33 UIKitCore 0x1942789d0 UIApplicationMain + 340 (UIApplication.m:5303)
34 Participant 0x1024fc874 main + 64 (AppDelegate.swift:16)
35 dyld 0x1b523de4c start + 2240 (dyldMain.cpp:1298)

Which iOS Meeting SDK version?
6.1.5.16935

Smartphone (please complete the following information):

  • Device: iPhone and iPad
  • OS: iOS 17.6, 17.5, and 16.3 so far.

Any word on this? Will there be an updated SDK soon?

Can anyone at Zoom comment on whether the latest SDK (6.1.10) fixes the crash reported above from 6.1.5?

I can confirm that this issue still exists with the 6.1.10.17500 release of the iOS Meeting SDK. Any help would be appreciated as we’ve now had to roll back twice due to these issues. @elisa.zoom or anyone else at Zoom that can provide some insight?

Hey @thinktapwork
Sorry for the late reply here! are you still experiencing this issue?

Yes, we have this issue with the latest Zoom Meeting SDK for iOS.

Hi @thinktapwork ,

We’ll fix this issue in our 6.2.0 version, which will be released around mid-September.
Thank you.

Elaine

@elaine.ku thank you. We’ll keep an eye out for the update.

1 Like