lukasIO

thank you, can you try with livekit-client v1.2.11? We fixed some things in that version that might be related to what you are seeing!

Hoping that https://github.com/livekit/client-sdk-js/pull/400 would fix the issue for you. Could you try with the main branch of this repo? (changes haven't been published to npm yet)

hm, would be great if you could turn on debug logs (`setLogLevel('debug')`) and post the entire logs for the failed connection sequence!

thank you for the logs! still not sure how to reproduce this unfortunately. we did some more compatibility related work for v1.3.0, you could give that a try!

hey, thanks for raising this, we've added the functionality as a helper class to the client-sdk-js in https://github.com/livekit/client-sdk-js/pull/489 which will be included in the next release :)

hi @oomaer can you run https://livekit.io/connection-test and post the results?

It's best to follow the messages that you get here. Try to host your server on a domain with a tls certificate as the first step and connect to it...

ah, that makes sense. have you tried connecting to `localhost` from the machine that hosts the server? If you are planning to deploy it in a local network you will...

what other room attributes do you have in mind? If there aren't too many, I think a granular event for recording could still make sense

@davidzhao does the additional event look ok to you?