New issue
Advanced search Search tips

Issue 764414 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 738918
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

pc.addTracks not adding tracks to peerconnection (chrome 61)

Reported by arun3...@gmail.com, Sep 12 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
1. Create peerconnection add a stream to it and check pc.getLocalStream()

It was working fine on 60 but failing on 61
3. 

What is the expected behavior?

What went wrong?
There is no addStream or addTrack event on the about:webrtc-internals,
Chrome never sends media to anyother client 

var pc1 = new RTCPeerConnection();

navigator.mediaDevices.getUserMedia({video: true, audio: true})
  .then(function(stream){stream.getTracks().forEach(function(track) {
          pc1.addTrack(track, stream);
        })})

pc1.onnegotiationneeded = e =>
  pc1.createOffer().then(d => pc1.setLocalDescription(d))
  .catch(log);

pc1.getLocalStreams()

Did this work before? N/A 

Chrome version: 61.0.3163.79  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
Cc: niklase@chromium.org
Owner: guidou@chromium.org
guidou, is this a known change? 
Components: Blink>WebRTC

Comment 3 by guidou@chromium.org, Sep 12 2017

Cc: hbos@chromium.org
Owner: hbos@chromium.org
addTrack is behind an experimental flag in 61 and its behavior is subject to change significantly since it's under development.

hbos@: Can you provide more details?

Comment 4 by guidou@chromium.org, Sep 12 2017

Cc: -hbos@chromium.org guidou@chromium.org

Comment 5 Deleted

Comment 6 by guidou@chromium.org, Sep 12 2017

Note that it's still behind an experimental flag in the current ToT.
Labels: Needs-Triage-M61

Comment 8 by guidou@chromium.org, Sep 13 2017

Status: Assigned (was: Unconfirmed)

Comment 9 by hbos@chromium.org, Sep 13 2017

Mergedinto: 738918
Status: Duplicate (was: Assigned)
The spec has undergone changes for how it handles media (interesting blogpost: https://blog.mozilla.org/webrtc/the-evolution-of-webrtc/). We're currently switching over from stream-based APIs (which are no longer in the spec) to track-based APIs (which are in the spec) including addTrack().

This is behind flag and is not ready. All effects of addTrack() are not yet supported.

Note that getLocalStreams() is not in the spec and is currently only modified as a result of addStream(), not addTrack(). Before unflagging addTrack() will affect getLocalStreams(), see  https://crbug.com/738918  (a prerequisite to implementing addStream() on top of addTrack()), but the stream-based APIs should eventually be deprecated since they are no longer in the spec.

Merging into the getLocalStreams() issue.

Comment 10 by hbos@chromium.org, Sep 13 2017

Correction: "... Before unflagging addTrack() we will make it affect getLocalStreams(), see ..."

Sign in to add a comment