David Zhao

@naziur604 are you able to reproduce this only with the Android SDK? If so please file it in the Android repo along with detailed logs from the client itself. Your...

Please provide the information requested in order for us to reproduce the issue. It's insufficient to state a specific problem with your own app. If you suspect it's an issue...

Thanks for the report. I think this is fixed by https://github.com/livekit/psrpc/pull/80. this will be released in 1.5.3

@kannonski @cruizba the fixes have been released in `1.5.3`. Do you want to give it a try and see if that resolves your issues?

Thanks for the confirmation @gysel !

The issue here is that your token has already expired when it's used against the server. For testing, you can create a token with a longer expiration.

you are not using the right server URL for that token. your token is generated for `mobiademo-***`, but in your code it's showing `mobia-***`. Tokens are specific to the server...

closing issue as it's stale. please reopen if issue persists

@gustavo-lighttwist thank you for getting this started. I like the direction of this.. The original design intention was to ensure that we do not mark a participant as ACTIVE unless...

Ah you are right, I see it in TransportManager. So the usecase here is to allow third-party/custom clients that do not support data channels to publish to LiveKit. I know...