This message was deleted.
# helpdesks
steep-balloon-41261
09/07/2023, 9:45 PMThis message was deleted.
a
acoustic-engineer-41666
09/07/2023, 11:55 PMcc @eager-zoo-16408
p
polite-kilobyte-67570
09/08/2023, 8:31 AMwhen you say it used to work previously, can you specify from which version to which version you upgraded when that behaviour started showing up?
f
freezing-ocean-2185
09/08/2023, 10:44 AMhello @polite-kilobyte-67570
freezing-ocean-2185
09/08/2023, 10:44 AMPreviously, I had the setup as shown below and it was working correctly:
freezing-ocean-2185
09/08/2023, 10:44 AM Copy code
import { DisplayContext, DisplayOptions, LiveKitRoom } from '@livekit/react-components';
<DisplayContext.Provider value={displayOptions}>
<LiveKitRoom
url={url}
token={token}
onConnected={(room) => {
setRoom(room);
onConnected(room);
room.on(RoomEvent.ParticipantConnected, () => updateParticipantSize(room));
room.on(RoomEvent.ParticipantDisconnected, () => onParticipantDisconnected(room));
room.on(RoomEvent.Disconnected, () => onRoomDisconnected(room));
updateParticipantSize(room);
}}
roomOptions={{
adaptiveStream: true,
dynacast: true,
publishDefaults: {
simulcast: true
},
videoCaptureDefaults: {
resolution: VideoPresets.h720.resolution,
},
}}
onLeave={onLeave}
/>
</DisplayContext.Provider>freezing-ocean-2185
09/08/2023, 10:44 AMNow, I have changed it to the following:
freezing-ocean-2185
09/08/2023, 10:45 AM Copy code
import { LiveKitRoom, VideoConference } from '@livekit/components-react';
<LiveKitRoom room={room} token={tokenUserLK} serverUrl={devUrl}
connect={true}
onConnected={() => {
console.log("done");
}}
>
<VideoConference />
</LiveKitRoom>freezing-ocean-2185
09/08/2023, 10:45 AMUnfortunately, it's not working as expected anymore. I made this change while updating to the current version "@livekit/components-react": "^1.1.7".
p
polite-kilobyte-67570
09/08/2023, 11:16 AMwhich version were you using before 1.1.7? just trying to find out what change in the library might be causing this
f
freezing-ocean-2185
09/08/2023, 1:35 PMBefore, I used this:
Copy code
"@livekit/react-components": "^1.1.0",
import { LiveKitRoom } from '@livekit/react-components'; Copy code
import { LiveKitRoom } from '@livekit/components-react';
"@livekit/components-react": "^1.1.7",freezing-ocean-2185
09/08/2023, 1:39 PMhello @polite-kilobyte-67570
p
polite-kilobyte-67570
09/08/2023, 1:45 PMwhich version of
livekit-clientf
freezing-ocean-2185
09/08/2023, 1:57 PMBefore, I was using this:
"livekit-client": "^1.3.2",
And now, I'm using this:
"livekit-client": "^1.13.2",
So, it seems I haven't actually updated it.
p
polite-kilobyte-67570
09/08/2023, 2:17 PMand the problem persists also with
1.13.2f
freezing-ocean-2185
09/08/2023, 2:35 PMyes
p
polite-kilobyte-67570
09/08/2023, 2:36 PMHm. Then I cannot think of a reason why it would behave differently to meet.livekit.io.
In order to debug this, we would need a minimal reproduction example from you that showcases that behaviour
f
freezing-ocean-2185
09/08/2023, 7:30 PM@polite-kilobyte-67570
Here, you can replicate this easily on https://meet.livekit.io. You open the pre-join and you turn off the camera and microphone, and then you open a new page with the same link, even in private browsing, and you do the same thing: turn off the camera and microphone. You enter the room without touching the control bar, you just close a page or tab of room and then it gets stuck on the other side.
freezing-ocean-2185
09/08/2023, 7:32 PMBut when you enable the microphone or camera in the pre-join, you won't encounter the problem.
p
polite-kilobyte-67570
09/11/2023, 6:47 AMconfirmed, thanks for the reproduction steps!
https://github.com/livekit/components-js/issues/630
✅ 1