-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
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
How to destroy the adaptor in react native #6399
How to destroy the adaptor in react native #6399
Comments
@mustafaboleken hope you can help sir, thank you |
Hi @vincemavill, Cheers |
@mekya any updates with this? thank you |
Hi @vincemavill, I just got back from the vacation. Preparing the guide, I will share it with you today. |
Hi @vincemavill, It's ready to test. You can use the published sample. Btw, due to not making a breaking change, I added extra functions to closing the local stream and WebSocket, reinitialing WebSocket, and some extra callbacks. Please let me know if this approach works for you. |
Hi @mustafaboleken, I happened to have the same issue with the adaptor and the changes fixes it! I only have one small issue; When you stop the stream and want start the stream again, you have to call the function/callback which calls Is there a way around this or is an additional adjustment needed in order to fix this? |
Hi @Jastc Let me update the sample. So, you don't need to double-click on it. |
I updated the sample. You can check it again. |
Hi @mustafaboleken, I'm not sure if you get a notification of it or not, but I added some comments to the changes you've made in the example code -> ant-media/WebRTC-React-Native-SDK#23 |
I've moved it to "In Progress" again to follow up closely in the sprint meeting. Thank you @Jastc |
Hi @Jastc For some reason I missed the notification, thanks for remind from here, I will check it. |
How can i destroy the adaptor Ant media, because the
pong command still showing on the logs and green dot doesn't disappear on the top right corner, even though I trigger the adaptor.stop(stream_id) and navigate back to other screen.
The text was updated successfully, but these errors were encountered: