https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
👀 3
e
how is the room disconnected? just 
room.disconnect()
?
b
@eager-raincoat-52616 For that if all participants get out of room. from backend(server) the mobile application will listen the disconnect socket event. through this event Mobile Application will remove that video calling screen and in dispose event of this video calling screen we have done room.dispose(); and room.diconnect();
e
is this accurate? 1. server force disconnects the connection. 2. mobile application listens for disconnect socket event 3. upon receiving disconnect event, calls `room.dispose`/`room.disconnect`?
b
as i know yes, every time the disconnect event is getting listened to mobile side.
e
and the app hangs during the 
room.dispose
/`room.disconnect` call? cc @freezing-lifeguard-43174
b
one of the side of the video calling the screen gets stuck when this happened and stopped the remotevideo track and localevideo track.
a
The iphone or Android phone calling the Samsung tab ends the call from phone. The phone is ok, the Tablet keeps the call going. It does not disconnect from the tablet and the call is stuck does not disconnect even when pushing end, keeps going on Server where we took logs. To disconnect needs needs forced app or device closure.
e
what flutter version are you using btw?
b
3.7.6
e
and the livekit_client sdk version?
b
Copy code
livekit_client: ^1.2.1
f
hey, is the audio and video connection not properly disconnected when disconnecting the room? so can the issue you are facing be reproduced in client-sdk-flutter/example?
If there are some steps to reproduce the issue, it may help us locate the bug quickly.
b
it is happening like 1/5 video call randomly. and for Video i have seen that the remotetrack is not available on that device.
f
so, as you mean 1v1 video call similar to facetime by video call? Or a multi-party video room?
b
one to one
f
This is more like a UI blocking issue. when you press the hangup button on the tablet, you can try to unpublish and stop localtrack, then call room.disconnect, and then return to the contact list page, BTW, you can try to track in logcat whether there is an exception throw,
okay, I found a logic problem in voip signaling, you use the iphone as the calling party, and the tablet as the called party, when your iphone hangs up, you need to send a separate notification to the tablet to inform the call is over, and let the tablet automatically hangup . As far as I know, livekit does not provide signaling logic similar to sip voip, so when the caller hangs up just leaves the room.
you can use the data-channel on the iphone to send a 
hangup
command to the tablet.
b
@freezing-lifeguard-43174 right we will do as you said but the problem is i am not able to reproduce this issue at debugg time and so cant see the loggs. so i have put the logic for disconnecting from call if you say i can share that part with you. if you can suggest be the better solution
a
We have handled this before, it has been working well for months. 2 weeks ago this issue came, we can reproduce it in many devices, but not all / all setups we do not know why
f
I think we need some device logs to locate the bug. when you press the hang up button, there should be an exception thrown to prevent the UI page jumping, am I right?
maybe you can try to connect to logcat and try to reproduce the issue in your video.
a
Thank you Duan! We aim to get the logs and if possbile try logcat..
d
2 weeks ago this issue came, we can reproduce it in many devices, but not all / all setups we do not know why
it'd be best to look through what's changed in your app between now and then. is it calling 
Room.disconnect()
? You can log an entry before and after disconnect to see if it gets through there
f
@aloof-businessperson-52833 https://github.com/livekit/client-sdk-flutter/commit/bf07a91c985addb62a1c080838d6fe6f7fbe09c8 This may be a related fix, as other users have reported that in 1v1 calls, the local client throws an exception when the remote participant exits.
Open in Slack
PreviousNext
Powered by