Closed vvedharaju closed 4 years ago
Oh, the issue is if call setEnabled(false) on a localTrack before publishing both the tracks. Whichever track I call setEnabled(false) on before publishing is not published when I later call setEnabled(true). Is that expected behavior? Do I need to explicitly publish the track again when I later call setEnabled(true)?
You can not publish a disabled track, but you can disable a published track.
got it 👍 just checking client.localTracks and publishing if its not already published
In 4.0.1, I noticed this happening frequently in rtc mode. So far, it has not happened to us in live broadcast mode. Please help!