App get crashed after ending the meeting

Description
App gets crashed when a user ends the meeting. Please check the description of the crash.

thread #1, queue = ‘com.apple.main-thread’, stop reason = EXC_BAD_ACCESS (code=1, address=0x200000010)
frame #0: 0x000000018dd6efb0 libobjc.A.dylibobjc_msgSend + 16 frame #1: 0x000000010231160c MobileRTC___lldb_unnamed_symbol12116$$MobileRTC + 124
frame #2: 0x000000018e42407c Foundation__57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_2 + 28 frame #3: 0x000000018dfb1ae0 CoreFoundationCFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 28
frame #4: 0x000000018dfb1b30 CoreFoundation___CFXRegistrationPost1_block_invoke + 68 frame #5: 0x000000018dfb0e28 CoreFoundation_CFXRegistrationPost1 + 396
frame #6: 0x000000018dfb0ac0 CoreFoundation___CFXNotificationPost_block_invoke + 108 frame #7: 0x000000018df29a58 CoreFoundation-[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1424
frame #8: 0x000000018dfb03f0 CoreFoundation_CFXNotificationPost + 1268 frame #9: 0x00000001021ca41c MobileRTC___lldb_unnamed_symbol4286$$MobileRTC + 4624
frame #10: 0x0000000102f5f924 MobileRTC___lldb_unnamed_symbol66548$$MobileRTC + 56 frame #11: 0x0000000102f0afe4 MobileRTC___lldb_unnamed_symbol65138$$MobileRTC + 2200
frame #12: 0x000000018dfd58c0 CoreFoundation__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32 frame #13: 0x000000018dfd55f8 CoreFoundation__CFRunLoopDoTimer + 928
frame #14: 0x000000018dfd4c6c CoreFoundation__CFRunLoopDoTimers + 280 frame #15: 0x000000018dfcfb14 CoreFoundation__CFRunLoopRun + 1896
frame #16: 0x000000018dfcf084 CoreFoundationCFRunLoopRunSpecific + 480 frame #17: 0x000000019821d534 GraphicsServicesGSEventRunModal + 108
frame #18: 0x000000019213f670 UIKitCore`UIApplicationMain + 1940

  • frame #19: 0x00000001008d4164 Power 20main at AppDelegate.swift:24:7 frame #20: 0x000000018de4ee18 libdyld.dylibstart + 4

Which version?
v4.6.21666.0428

Hi @pandiyaraj,

Thanks for the post. Could you provide the full crash log for us to further investigate? Could you have a try with the latest version and see if this issue persists?

Thanks!

Hi Carson,

Thanks for the acknowledgment, above crash log only i am received .
I’ll use the latest version and let you know the same

Thanks for the info. I have forwarded this to the engineering team for further investigation. Will get back to you shortly.

Hi @pandiyaraj,

Unfortunately, the provided crash info does not provide enough information for us to approach the issue you are facing. It will be hard for us to troubleshoot this without the full crash log. Could you help to see if you are able to get the full .crash log? How often does this happen? Is this issue reproducible with our demo app? If so, could you provide the steps to reproduce this issue?

Thanks!