Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Update from 61.0.2 to 62.0 has broken my webrtc application

  • 3 replies
  • 1 has this problem
  • 20 views
  • Paskiausią atsakymą parašė cor-el

more options

Hello, I am involved in developing an application that uses WebRTC for video calling.

Prior to yesterday my FF browser was at version 61.0.2 and the application could make video calls between FF / Chrome and apps running on Android and iOS

Today, I was unable to make calls to/from FF 62.0. Calls made using Chrome to Chrome work fine. Two colleagues were also able to make calls with older FF 61.0.2 and then no longer, after upgrading to FF 62.0

We are using the PeerJS library

What WebRTC related changes have been implemented between 61.0.2 and 62.0?

Thank you

Hello, I am involved in developing an application that uses WebRTC for video calling. Prior to yesterday my FF browser was at version 61.0.2 and the application could make video calls between FF / Chrome and apps running on Android and iOS Today, I was unable to make calls to/from FF 62.0. Calls made using Chrome to Chrome work fine. Two colleagues were also able to make calls with older FF 61.0.2 and then no longer, after upgrading to FF 62.0 We are using the PeerJS library What WebRTC related changes have been implemented between 61.0.2 and 62.0? Thank you

All Replies (3)

more options

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/62 might help.

Also note, if you're developing a web application, I'd suggest testing it with the current Firefox Beta so then you can catch new changes before they are released.

more options

Hi Tyler, thanks, I have been reviewing the 62 release notes and nothing there (including the developers' notes on Media Webrtc etc) leaps out at me as being an obvious cause.

Is there a more detailed breakdown of changes related to WebRTC available? I note your point about the beta channel. But didn't pick this one up in beta...

more options

Did you check the Web Console and possibly the Browser Console for error messages?