This message was deleted.

hi @faint-refrigerator-4215, that’s definitely not expected! A couple of things to track this down • Are you using cloud/self hosted instance? in case of self hosted, can you check if the same thing happens when using meet.livekit.io with the custom connection option and provide your server url and a token • which components version are you using? (please update to the latest npm version in case you haven’t) • Could you post the logs you’re getting? • Does the parent component constantly re-render for you ? (just put a console.log(“render”) in the component above

<LiveKitRoom>

The component is constantly rerendering, but the one that is is the LiveKitRoom itself and the offending prop is

children

Hi @polite-kilobyte-67570, I'm working with Jamie on this issue as well and want to add some things in case it's helpful for debugging. We're using this hook to fetch the token almost identically to have livekit does it in livekit meet here. That

useToken

hook is running over and over again, and you can see the

log.debug('fetching token');

show up multiple times in the logs Jamie included. Is there anything we should be looking out for that might cause

useToken

to get called on a loop continuously?

in your

useToken

implementation, can you try to replace the

options

in the dependency array with

[tokenEndpoint, roomName, JSON.stringify(options)]

. this would prevent causing re-renders (and we’ll probably add this optimization to the components-js repo as well)