Sometimes we experience the streamIdInUse error, because the user still has an open
connection on the same device, but in another tab/window.
We tried to automatically tackle this by calling the REST API's /broadcasts/<streamid>/stop/ whenever the same client tries to connect/start publish, but due autoRepublishEnabled publishing will be resumed after a short break.
Disabling autoRepublishEnabled doesn't seem to be a good idea, because doing so will cause more troubles.
Anyone had the same issue and implemented a way to stop publishing across all open windows/tab on the client side?
Example scenario: User has an open tab/window (A) on mobile where he already started a broadcast/connection and forgot to stop the stream. He opens another tab/window (B) and see "streamIdInUse" when he tries to publish.
Instead of telling him "check your open tabs/windows and disconnect" we want to this automatically.
Question
lars schwarz
Sometimes we experience the streamIdInUse error, because the user still has an open
Anyone had the same issue and implemented a way to stop publishing across all open windows/tab on the client side?
Example scenario: User has an open tab/window (A) on mobile where he already started a broadcast/connection and forgot to stop the stream. He opens another tab/window (B) and see "streamIdInUse" when he tries to publish.
Instead of telling him "check your open tabs/windows and disconnect" we want to this automatically.
Thanks: Lars
Link to comment
Share on other sites
Top Posters For This Question
1
1
Popular Days
Jul 22
1
Jul 23
1
Top Posters For This Question
lars schwarz 1 post
Cem K1l1 1 post
Popular Days
Jul 22 2021
1 post
Jul 23 2021
1 post
1 answer to this question
Recommended Posts