Not enough arguments to mozRTCPeerConnection.getStats

[oleg-ria]

Hi, in firefox it does not work. Got error "Not enough arguments to mozRTCPeerConnection.getStats". Error fires on line 155

[ulifigueroa]

That's because in the Firefox implementation the getStats function need to receive a MediaStreamTrack, like this:

peer.getStats(
    mediaStreamTrack,
    function (res) {
        var items = [];
        res.forEach(function (result) {
            items.push(result);
        });
        cb(items);
    },
    cb
);

[ulifigueroa]

#2

[igorpavlov-zz]

+1

[ulifigueroa]

@muaz-khan you should close this issue and pull request #2 since you already pushed the change to the master branch.

[simkesd]

@ulifigueroa How did this work out for you?

From my understanding window.getStats from this library is actually calculating and returning stats that cover both audio/video (at least for Chrome). Aren't you restricting it to just single track (audio or video)?

[ulifigueroa]

@simkesd I'm sorry, I don't know, I posted this fix in 2015 so probably it's not up to date

[bFraley]

I'm working on an RTC stats UI for an application and came across this project, and this issue. For others, and contributors who want to look at updating this project:

The current Chrome implementation is RTCPeerConnection.getStats with info here: https://www.chromestatus.com/feature/5665052275245056

Mozilla uses the RTCStatsReport interface that provides a variety of RTC connection information and is documented here: https://developer.mozilla.org/en-US/docs/Web/API/RTCStatsReport