Crash from MobileRTC SDK due to unrecognized selector

Meeting SDK iOS
1

Description
For quite some time the largest crash by incident count in our app has been due to an unrecognized selector SIGABRT originating in the MobileRTC code. We recently added a crash reporter that revealed a bit more about the issue. Specifically, it appears that the Zoom SDK is attempting to access the rootViewController property of one of our UIViewController instances. Since rootViewController is not defined on UIViewController it would crash with “unrecognized selector sent to instance”. To attempt to resolve the issue we implemented a property called rootViewController and applied our own logic to return a valid UIViewController (for instance, the first view controller in a UINavigationController).

That seems to have stopped that crash. However, we now are getting a new case of “unrecognized selector sent to instance”, undoubtedly because we are now past the first crash but we are giving it a view controller type that it does not expect. Now it is attempting to access a property named originTitle. We plan on doing the same thing we did with rootViewController to get past this issue, but we wanted to report it and hopefully get a true resolution from Zoom.

Feel free to get in touch for more details, although we are unable to reproduce this issue so it is hard to troubleshoot.

Which iOS Meeting SDK version?
All recent SDKs.

To Reproduce(If applicable)
Unable to reproduce

Smartphone (please complete the following information):

  • Device: iPhone / iPad
  • OS: iOS 15, 16, 17
2

Wanted to see if there are any updates on this.

3

It appears that our efforts to fix this by providing implementations for the expected properties is just delaying the crash, i.e., we fix one and instead it crashes right after due to something else. Now that we included an originTitle it crashes with the following:

libobjc.A.dylib
_class_lookUpIvar(objc_class*, ivar_t*, long&, objc_ivar_memory_management_t&)
libobjc.A.dylib
object_getIvar
MobileRTC
0x101c38000 + 242628

Would love to see this fixed as it is the number one crash by far.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.