https://livekit.io logo
Join Slack
Powered by
# helpdesk
  • w
    yep makes sense
  • w
    question about behaviors: is the 
    TrackSubscribed
    callback supposed to fire in this case: 1. User A joins 2. User A publishes 3. User B joins 4. User B gets a 
    TrackSubscribed
    callback fired right after 
    connect
    completes
  • w
    Trying to figure out if users who join a call that already has publishers is supposed to receive that 
    TrackSubscribed
    event or not
  • w
    or if there is some other event user B should hook into in order to subscribe to user As stream
  • d
    trackSubscribed
    should always be fired when a new track is sent to the client.
  • d
    tho.. there’s an order of operations issue here..
  • w
    so if a client joins and there already publishers, will those existing tracks be sent to the client that just joined?
  • d
    yeah it should
  • w
    ok we aren't seeing that consistently
  • d
    I see.. so there’s another issue here..
  • d
    which is.. we talked about having connect return after ICE connectivity is established
  • d
    if we do that.. then it’s possible that some of the track subscribed are fired off before the 
    trackSubscribed
    listeners are registered
  • d
    so we might need to adjust that behavior.. so that there isn’t a chance that you’d miss events
    👀 1
  • d
    that’s not what I’m saying happened here.. btw..
  • d
    this could be a server based issue
  • w
    gotcha I'll let you think through it further. In the meantime I will say I'm having a tough time gathering client logs around that 
    setRemoteDescription
    error
  • w
    if it happens again I'll try and gather the logs
  • d
    cool thanks!
  • c
    Summarizing our 3 main issues right now: • Livekit.connect -> sometimes doesn’t return answer (no peer connection happens) but connect returns so it looks like it connected to the client • after connect onTrackSubscribed not always fired (might be related to above but i think i’ve seen it outside of that) • room.unpublishTracks doesn’t properly remove tracks from peer They might be on our end or your end but we’re seeing these issues now. I think once we get through these 3 we should be pretty much “working”
  • d
    are these all on 0.2.4?
  • d
    also.. if there’s a way for me to try your app, maybe I can spot the issue w/o having you dig through logs
  • w
    0.2.4 yes
  • w
  • w
    make an account and I'll activate it
  • w
    me and furqan are on a call now
  • d
    lol awesome
  • w
    $10 says you'll see some of these issues right off the bat
  • d
    hahaha.. I like the confidence.. but just put my $10 on GME calls
  • w
    ONE OF US
  • d
    better odds there 🙂
1...111213...91Latest