Video call continues in background when user is kicked out from server about capacitor-jitsi-meet

[calvinckho]

@maxfloden Sorry for the late response. Thanks for sending the console log. I noticed the following:

1. The SDK reports that the jitsi conference termination -> cleanup -> viewDidDisappear all happened successfully.
2. however, the SDK is trying to rejoin the conference immediately after the termination and cleanup is completed.

Can you check your code on why the Jitsi.joinConference() is being triggered after the server crashes/the user was kicked out? Sometimes when leaveConference() and joinConference() happens too close to each other, the server will keep the connection active as if the user has never left the conference.

PS. I also saw the Angular zone warning. You may want to check why the system is warning you about the onConferenceLeft() event being triggered outside of the Augular zone.

⚡️ [debug] - Event onConferenceLeft ⚡️ [warn] - Navigation triggered outside Angular zone, did you forget to call 'ngZone.run()'?

[maxfloden]

I don't do anything to reconnect in code. I have also tested this on the iOS-SDK 9.2.0 and same thing happens there.

This is how I recreate it, it seems to be possible to recreate every time:

• Connect to meeting from my device (iOS) + connect from desktop Chrome in two different tabs, so total is three users connected in meeting to avoid p2p
• Restart jitsi server
• Browsers will show "reconnecting" but app will close video window but iOS green indicator still lit (video still recording)
• When server is upp again, if I reconnect from browser I can still see video from iOS user

So obviously iOS managed to reconnect to server in background. I do not have anything in my code to reconnect, so my guess is that this is handled by the iOS SDK.

P.s. Re Angular zone, I cannot find anything in my code but maybe I don't know where to look. This is a Ionic7 / Angular 17 / Capacitor5 project.

[calvinckho]

Hi @maxfloden, thanks for providing more details. Based on your description, the issue is related to a potential bug with the SDK and not with the plugin. Perhaps you can try to create an issue at the Jitsi repo?