Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Update from 61.0.2 to 62.0 has broken my webrtc application

  • 3 回覆
  • 1 有這個問題
  • 20 次檢視
  • 最近回覆由 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

所有回覆 (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?