client-sdk-js
client-sdk-js copied to clipboard
Share screen request window not show up after page reload on Edge on Windows 11
Describe the bug
User join a Room and publish sharescreen track to server. The first time page loaded, sharescreen window request showed up, everything worked fine. After that, reload page and share screen request window on Edge didn't show up.
Reproduction
room = new Room({
adaptiveStream: false,
videoCaptureDefaults: {
resolution: {
width: 1280,
height: 720,
frameRate: 30,
},
},
publishDefaults: {
videoEncoding: {
maxBitrate: 1_500_000,
maxFramerate: 30,
},
screenShareEncoding: {
maxBitrate: 1_500_000,
maxFramerate: 30,
},
audioBitrate: 20_000,
dtx: true,
// only needed if overriding defaults
},
dynacast: true,
});
shareScreenTracks = await room.localParticipant.createScreenTracks({ audio: false });
Logs
Clients Browser: Microsoft Edge Version 121.0.2277.83 (Official build) (64-bit)
System:
OS: Windows 11 - 23H2 (OS build 22631.3085)
Node JS: v16.20.2
Windows default sound output device: Speakers
Windows other audio output device: Headphones
Binaries:
Node: v16.20.2
npm: 8.19.4
npmPackages:
livekit-client: 1.4.1
System Info
No responses
Severity
annoyance
Additional Information
No response
Hi,
thanks for the report. You selected blocking an upgrade - is this a change in behaviour when trying to update the livekit-client version?
I see that you currently have v1.4.1 installed, can you try with the latest version?
Hi, sorry i mistakenly selected the blocking an upgrade option it should be annoyance.
About upgrading to latest version, I've tried updated to the latest version 1.15.10 but the problem still remained.
can you reproduce this on meet.livekit.io?
If so, please post the complete client logs. If it's not reproducible on meet.livekit.io we'll need a ready-to-run reproduction sample
I have a quite a similar with few users which are able to share their entire screen on Mac only the first time the page is loaded.
@lebaudantoine make sure you are on the latest version of the SDK and if the issue persists, please open a new issue with repro steps, the issue here was windows specific and I'll close it now due to the missing reproduction