App is still crashing in iPhone also while leaving the meeting with latest SDK ver 5.13.5
When i typed bt all;image list; on xcode console after the crash, it printed following error
error: bt [ | all]
But i got some results when i typed bt all and then image list on the Xcode console. Please download the files from below links which contains the output i got after typing bt all and image list
I also noticed when i leave the meeting then meeting status changes to connecting after disconnecting in onMeetingStateChange delegate method.
Is there anything we need to do when meeting status changes to disconnecting? I mean why the status is changing from disconnecting to connecting while leaving the meeting.
We’re now working on it and found some possible issues that cause the crash, but we cannot reproduce the problem you’ve mentioned to prove our finding. Would you please provide the detailed step to reproduce the issue?
Thank you
Is there an update about the steps to reproduce the issue? We were trying to find out the root cause of this issue but would like to have your help to provide the steps.
Thank you
Our team has tried the same step as yours but we cannot reproduce the issue. We had looked into the swift file that you provided and wondering if the foundation onClickedEndButton is to leave the meeting since it didn’t use the leaveMeetingWithCmd function.
Just wondering where is the function service.leaveMeeting from since we do not have this function in our SDK. We only have function leaveMeetingWithCmd in the meeting service interface.
Thank you
Regarding service.leavingMeeting, I am referring for below code. Here we are using object of getMeetingService to leave the meeting.
if let service = MobileRTC.shared().getMeetingService(){
service.leaveMeeting(with: .leave)
service.delegate = nil
}
Is there anything else we need to do while leaving the meeting and did you find anything which we are missing in ZoomWebinar.swift which i shared earlier ?
Will really appreciate if you can please let us know if we are missing something here.
Hi @elaine.ku@carson.zoom
Can you please provide your feedback regarding the code we shared earlier and let us know if we are missing something in the implementation?