We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Despite calling the adaptor.stop function to terminate the connection, I am still encountering errors in the callback error handler.
Steps to reproduce
###Expected behavior Once the host stops the broadcast, the callback should also stop.
###Actual behavior Once the app starts the broadcast, then the host stops the broadcast, and then we use the below code: adaptor.stop(roomId);
But after this, the callback always throws an error:
callbackError >> no_active_streams_in_room {"command": "error", "definition": "no_active_streams_in_room", "room": "65f1a02a1980acedde5e4721"}
It uses a lot of memory and batteries. It is also causing app crashes.
The text was updated successfully, but these errors were encountered:
This might be related to "Problem 2" from #4071 (comment)
Sorry, something went wrong.
Hi @MaZZly It can be. I will work on React Native at the weekend. I hope these issues will solved until Monday :)
mustafaboleken
No branches or pull requests
Short description
Despite calling the adaptor.stop function to terminate the connection, I am still encountering errors in the callback error handler.
Steps to reproduce
###Expected behavior
Once the host stops the broadcast, the callback should also stop.
###Actual behavior
Once the app starts the broadcast, then the host stops the broadcast, and then we use the below code:
adaptor.stop(roomId);
But after this, the callback always throws an error:
callbackError >> no_active_streams_in_room {"command": "error", "definition": "no_active_streams_in_room", "room": "65f1a02a1980acedde5e4721"}
It uses a lot of memory and batteries. It is also causing app crashes.
The text was updated successfully, but these errors were encountered: