-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Perfect negotiation sample not working on Android Chrome #1457
Comments
I am actually getting the same silent failure on this sample as well https://webrtc.github.io/samples/src/content/peerconnection/pc1/ same device, pixel 4a chrome 83.0.4103.106 The logs seem ok but no video is exchanged between the two peers, the left side shows the localstream but the right side only shows a black canvas when hitting the call button. |
I see that you tied this issue to an ipv6-only problem we've seen in other contexts. This is likely a Chrome bug, not a bug in the page; if verified, we'll probably move this to crbug.com. |
I'm not sure how to run that command on Android but if I check in the device settings I can see that there are 4 addresses listed: 3 IPv6 addresses (one of them link-local |
Screenshot the device settings page? Pinging @henbos |
ping. I think we've made some progress on Android ICE bugs. |
Please read first!
Please use discuss-webrtc for general technical discussions and questions.
Note: If the checkboxes above are not checked (which you do after the issue is posted), the issue will be closed.
Browser affected
Chrome (83.0.4103.106) on Pixel 4a
Description
running the perfect negotiation does not give expected results, although the logs seem correct no remoteVideo is rendered on either polite or impolite peer side
https://webrtc.github.io/samples/src/content/peerconnection/perfect-negotiation/
Steps to reproduce
Start both peers connection and swap the sending track
Expected results
additional remote video element is added next to local video elements
Actual results
only local video elements are displayed, no additional element added
The text was updated successfully, but these errors were encountered: