1367049 - Voice chat on Discord is stuck on RTC Connecting, regression

Status: RESOLVED FIXED

(Web Compatibility :: Desktop, defect, P1)

Description

[myuumyuutsu]

Attachment: annoying.png

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170523030206

Steps to reproduce:

Go to Discord https://discordapp.com/ and join channel with Voice chat for example https://discordapp.com/invite/cVA5w and then connect to voice chat

Also this started happening from this build https://hg.mozilla.org/integration/autoland/rev/b954d11db347 but I don't really know how to use Mozregression so it could be false


Actual results:

After connecting it gets stuck on RTC Connecting


Expected results:

It should have connected fully

Comment 1

[Flore Allemandou [:flore]]

I just tried on my regular nightly and I saw the same issue, but when I tried on a fresh nightly profile, it works correccttly.
Can you check on a new fresh profile? 

https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles#w_creating-a-profile

Comment 2

[myuumyuutsu]

Tried to use two new profiles on one of which I used my account and the other one where I used unclaimed account, both are stuck in the same way.

Comment 3

[Loic]

Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=186d77e982061443dc7ef1dd662da59b2928de18&tochange=0e21ef2001d30597c6b8a1df9d80c3bd442ab93b

Nils Ohlmeier [:drno] — Bug 1323723: reject setup value actpass in answers. r=bwc
Nils Ohlmeier [:drno] — Bug 1323723: enforce a=setup in SDP offers. r=bwc

Comment 4

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

P1 until we learn if this is a site bug.

Comment 5

[Nils Ohlmeier [:drno]]

After Firefox creating the offer with 'a=setup:actpass' the SDP answer from the Discord server contains 'a=setup:actpass'. This is clearly not spec compliant. Older versions of Firefox used to ignore this. The answerer has to choose either 'a=setup:active' or 'a=setup:passive', where active is the recommended role as per spec.

Comment 6

[Loic]

I'll reopen this bug and change it to TE because Discord is an important VoIP application used by many gamers worldwide. We need to contact Discord and be sure they fix the issue on their side before the release of FF55.

Comment 7

[Mike Taylor [:miketaylr]]

Adam, can you try to get us in touch with Discord? See Comment #5 for an explanation of what they need to change their SDP answer to -- thanks!

Comment 8

[Adam Stevenson [:adamopenweb]]

Trying to reach Jesse Howarth on Twitter:
https://twitter.com/AdamOpenWeb/status/867843357556518912

Comment 9

[Adam Stevenson [:adamopenweb]]

We got a quick response: "we're aware of it and planning on fixing the bug before Firefox 55 releases."

Comment 10

[Nils Ohlmeier [:drno]]

I have no idea how important Discord is. Is it worth adding them to our manual test cycles, or do we have close enough contacts with them to talk to them about their testing (because looking at their signaling I would expect a lot more problems in the future)?

Comment 11

[Loic]

(In reply to Nils Ohlmeier [:drno] from comment #10)
> I have no idea how important Discord is. 
Some numbers in this recent aricle:
http://mashable.com/2017/05/16/discord-two-year-anniversary-growth-stats/

This service is really popular in gaming communities in US/Canada and Europe.

Comment 12

[Adam Stevenson [:adamopenweb]]

I agree it's very popular (I use it too).

Discord's website is also ranked 109 in U.S by Alexa. That said, it's not clear how much voice chat usage happens through web vs. apps.

We can try to discuss further with them if we think it's valuable.

Comment 13

[Liz Henry (:lizzard Please n-i to RyanVM, jcristau, or pascal)]

Let's track this for 55 to make sure it gets resolved.

Comment 14

[Mike Taylor [:miketaylr]]

Adam, can you test if this is still an issue?

Comment 15

[Adam Stevenson [:adamopenweb]]

Seems like this is fixed. I get to "Voice Connected" in both Firefox 55 and 56 for OSX.

Let's close this report, thanks everyone!

Comment 16

[Mike Taylor [:miketaylr]]

Thanks Adam!

Comment 17

[bgr]

This started happening again, reported by multiple users: https://support.discord.com/hc/en-us/community/posts/360062784132-RTC-Connecting-after-Windows-10-0-18363-Firefox-76-0-1-update-

Comment 18

[Josh Matthews [:jdm]]

I observed this in FF 76 on May 10.

Comment 19

[Adam Stevenson [:adamopenweb]]

Thanks! Discord has fixed and should be pushing out the update soon.

Comment 20

[carado]

Hi, I'm encountering this issue again.
I'm using firefox 85.0.2 (64-bit) on archlinux with pulseaudio as sound server.
I was in a discord call, with everything working just fine; I disconnected, reconnected, and then suddenly it was stuck on "RTC Connecting". The following didn't help:

• rebooting my computer
• clearing all cookies and local data
• using a different firefox profile
• trying without my VPN
• rebooting my router
• stopping and uninstalling pulseaudio
• trying out different servers than Europe (my default)

Voice chat works just fine on the discord desktop app, however.

Comment 21

[carado]

Oops, nevermind, the following fixed it:
Going into my discord voice settings and using the "Reset Voice Settings" button.
Sorry about the message.