LiveKit Community

and any news on this?

```  disconnect() {
    // TODO: handle disconnection
  }```

we want to call it to give the server a proper indicator to clean up a users stuff

not yet :upside_down_face: , focused on stabilizing the server at the moment

just pushed! check out the metadata APIs, this should allow you to pass data like {seat_id} via the token

Wonderful, I just read through those changes. Will give them a test now

<@U01KZ61GV5Z> I read through the commits. Is there anything addressing this? <https://twitter.com/_pion/status/1359263749853437952?s=21>

no, that won't be addressed with this build

targeting 0.4.0 to switch to a workaround, but it'll require protocol changes.

furqan mentioned that there are some folks running it that confirmed 4 person calls work fine? Is that still true?

could you link me to that? I don't see it in the github org

I'm working through all those issues but wondering you have something I can use. We want to use the demo app as a baseline to assess if bugs are happening due to lk or due to our app

they are all on our radar, moving to dedicated PCs would help with most of them. will keep you posted

nice i think #2 is probably some concurrency / out of order issue. i think i can make it a little better by moving some things later on in our flow (instead of connecting on page load do it after user clicks join). From a UX perspective i like hiding things so that things feel faster.

it won't remove it but it makes it "better"

#1 is a big blocker for us that looks like a regression

word.. #2 should be resolvable too. that's the most predictable one of the group

does this message look like anything to you? <@U01KZ61GV5Z>

```could not find published track```

along with it are two track sids

```"could not find published track" "PA_HKWWHG87Y9NX" "TR_rtMC9tC3noTw"```

I can't find any reference to that message "could not find published track" in either our codebase or yours

oh wait I don't think I have the latest lk code one sec

<https://github.com/livekit/client-sdk-js/blob/main/src/room/participant/RemoteParticipant.ts#L65>

so one of our bots is trying to publish, but ran into that error

how are we supposed to recover from this?

I don't think the error is thrown so I can't detect it and try to republish

please advise on how we should handle that error because I don't completely understand when it would even happen

interesting.. which browser does the bot use?

exact version doesn't matter too much.. this isn't in the publish flow

no tracks coming in to the other particpants

but yeah the error got printed and the tracks never got published (and therefore were never subscribed to by any other participants)

we send metadata down first before firing the track subscribed event, so that we could align the track IDs..