Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Learn More

WebRTC Codelab not working on firefox beta and developers edition

  • 2 odpowiedzi
  • 1 osoba ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od Dr.NO

more options

Neither codelab(https://bitbucket.org/webrtc/codelab) or my webrtc example(https://drive.google.com/folderview?id=0B-0S2tp3jVroVlZKMHNYdG5MUDQ&usp=drive_web) works on firefox beta or developers edition. In the console it gives ICE Error. But both of them works in chromium, chrome and firefox v31.0

Neither codelab(https://bitbucket.org/webrtc/codelab) or my webrtc example(https://drive.google.com/folderview?id=0B-0S2tp3jVroVlZKMHNYdG5MUDQ&usp=drive_web) works on firefox beta or developers edition. In the console it gives ICE Error. But both of them works in chromium, chrome and firefox v31.0

Wszystkie odpowiedzi (2)

more options

Do you have the version of Beta that this was tested on? This will help identify where this stopped working, also have you opened up an issue with the codelab as well?

more options

The more recent versions of Firefox implement full trickle ICE. This means the offerer will get ICE candidates right after creating the offer. But on the answerer side Firefox will only allow you to add ICE candidates after setRemoteDescription() has been called. From briefly looking at the code in codelab and the Google Drive you provide I think both might either drop early ICE candidates completely or try to add them before setRemoteDescription was called. In both cases the connection most likely won't get established as ICE candidates will be missing.