Basic WebRTC Call setup not working in Chrome (RTCPeerConnection) |
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Steps to reproduce the problem: 1. Go to https://w3c-test.org/webrtc/simplecall.html 2. Observe that you could setup a basic WebRTC Call What is the expected behavior? WebRTC Call setup works and Video is on display What went wrong? Chrome latest version (62.0.3202.75 (Official Build) (64-bit)) Throws Error //gFirstConnection.addTrack is not a function TypeError: gFirstConnection.addTrack is not a function at https://w3c-test.org/webrtc/simplecall.html:45:24 at Array.forEach (<anonymous>) at Test.getUserMediaOkCallback (https://w3c-test.org/webrtc/simplecall.html:44:29) at Test.step (https://w3c-test.org/resources/testharness.js:1489:25) at https://w3c-test.org/resources/testharness.js:1513:35 at <anonymous> /// and It could not setup the basic Call. Did this work before? N/A Chrome version: 62.0.3202.75 Channel: stable OS Version: OS X 10.12.6 Flash Version: Works like a Charm in Safari, Firefox. Not working in Opera (So clearly a Chromium Issue)
,
Oct 30 2017
,
Oct 30 2017
,
Oct 31 2017
Able to reproduce this issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #62.0.3202.75 and latest canary #64.0.3253.3. This is a non-regression issue as it is observed from M50 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Oct 31 2017
,
Nov 1 2017
This is a feature under development (and a large part of the WebRTC 1.0 work), it's currently behind a flag. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dtapu...@chromium.org
, Oct 30 2017