-
Notifications
You must be signed in to change notification settings - Fork 65
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
iceConnectionState and iceGatheringState are never updated #58
Comments
onaddstream is fired actually. But oniceconnectionstatechange event is not fired. We can add the stream to view on the page, but we don't know if we were connected or not. So we can see the black screen if the connection wasn't established but onaddstream fired. |
Thanks for logging and investigating all of these issues @pantaoran - we're finding the same thing. Since you posted, have there been any changes to note with regard to the iceConnectionState not changing? It'd be really awesome to have this fixed in Bowser as it's the only way to verify that a connection has been successfully established between two peers - a fairly important piece of most WebRTC implementation puzzles. |
@stefhak any thoughts on this? Could it have been resolved in your latest fixes? |
I added the necessary parts to the C API for ice connection state I believe though the aggregation between components would need to be checked in case it is specified somewhere. And we could also implement an ice gathering state property fairly easily. |
Awesome, thanks so much for your work on this. When might we expect this to be updated in the AppStore? |
These two fields always remain in the NEW state and never change on Bowser, which makes it difficult to know if a connection has been established or not.
Please implement those state machines as specified.
Also, as I noted #53 onaddstream never gets called on Bowser, this might be related?
The text was updated successfully, but these errors were encountered: