Skip to content
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

Open
3 tasks done
felix-aivitex opened this issue Jun 22, 2021 · 5 comments
Open
3 tasks done

Perfect negotiation sample not working on Android Chrome #1457

felix-aivitex opened this issue Jun 22, 2021 · 5 comments

Comments

@felix-aivitex
Copy link

felix-aivitex commented Jun 22, 2021

Please read first!

Please use discuss-webrtc for general technical discussions and questions.

  • I have provided steps to reproduce
  • I have provided browser name and version
  • I have provided a link to the sample here or a modified version thereof

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

@felix-aivitex
Copy link
Author

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.

@alvestrand
Copy link
Contributor

I see that you tied this issue to an ipv6-only problem we've seen in other contexts.
Can you possibly share the result of running "ip addr" (linux) or similar commands for other OSes so that we can see what interfaces and addresses are available?

This is likely a Chrome bug, not a bug in the page; if verified, we'll probably move this to crbug.com.

@felix-aivitex
Copy link
Author

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 f80:...) and one IPv4 (the device ip address on the local network)

@alvestrand
Copy link
Contributor

Screenshot the device settings page?
Does your network have IPv4 connectivity?

Pinging @henbos

@fippo
Copy link
Collaborator

fippo commented Apr 25, 2022

ping. I think we've made some progress on Android ICE bugs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants