1186543 - RTCIceServer.url is deprecated! Use urls instead

Status: RESOLVED FIXED

(Hello (Loop) :: Client, defect, P5)

Description

[Peter deHaan [:pdehaan]]

Using FF40 and making a test call this morning.

Noticed this pop up in my dev tools console (about 6 times). Not sure if this is even us (or something up/down stream) or if it is actionable:

> RTCIceServer.url is deprecated! Use urls instead.     <unknown>

I can't even find that in the code, and devtools "helpfully" says <unknown>, so this is pretty much the most garbage bug filed ever. #seesomethingfilesomething

Comment 1

[Mark Banner (:standard8)]

This is an exception from webrtc here:

http://hg.mozilla.org/mozilla-central/file/e7434cafdf2f/dom/media/PeerConnection.js#l503

This is from bug 1115998 which landed in FF 38. Its harmless at the moment.

The warning is due to the way the ice servers are configured by Tokbox - which is supporting backwards compatibility. However, I think the ice server config could be changed to provide both urls & url, hence needinfo to Tokbox to see if they can tweak the settings for this at some stage.

Comment 2

[:shell escalante]

currently harmless console message

Comment 3

[Ted]

(In reply to :shell escalante from comment #2)
> currently harmless console message

It isn't harmless anymore. ICE fails when one or both of the peers are using Firefox. The error is as posted above.

> RTCIceServer.url is deprecated! Use urls instead.     <unknown>

Comment 4

[Mark Banner (:standard8)]

Mike, re this and other warnings about deprecated interfaces [1], would it be possible to get the SDK updated to prefer the official APIs rather than checking/using the prefixed ones first?

[1] (WebRTC interfaces with the "moz" prefix (mozRTCPeerConnection, mozRTCSessionDescription, mozRTCIceCandidate) have been deprecated.)

Comment 5

[msander]

This is fixed in the 2.7.3 version of the SDK.

Comment 6

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Does that mean I can finally fix bug 1116766, or do we first need to update to that sdk version or something?

Comment 7

[Mark Banner (:standard8)]

Unfortunately we need to wait for the upgrade first (bug 1237677) which is blocked by an issue with the new sdk (bug 1248407).

Comment 8

[Mark Banner (:standard8)]

I've just relanded bug 1237677, so this is fixed.

Jib: Note it'll be at least next week before we get this out to nightly builds, and probably 1-2 weeks before we ship it on standalone.