This message was deleted.

We have not seen such long delay before screenshare is received. LiveKit itself does not add meaningful latency - it just forwards packets from the publisher to subscribers. It sounds like something is going on with the publisher itself. Some questions: 1. When do you receive the TrackPublished event on the subscriber side? 2. How are you performing screen share? Can you share the code that you are using? For pagination, you can convert

room.participants

into a list and paginate that. The data is all loaded on the client side, so pagination should be quite straight forward.

https://github.com/owaisansarii/debug/tree/main I have removed most of the code that is not needed, if you need anything else please let me know. Regarding the pagination thing, It's hard because the list updates frequently, so if a user is shown once on first page and he leaves and join again, then he might be visible on second page too, we can handle this by limiting the number of user to be shown but I was wondering if there's any better way to handle it

Hi @dry-elephant-14928 @magnificent-art-43333 can you please help us with this ?

Hi @dry-elephant-14928 , I created an Android build from the React Native example from client sdk react native repo. However, when I share the screen, the mobile screen is not visible to anyone.

we have not had a chance to look. but will try to get to this tomorrow

Thanks