Fix issue with older browsers erroring upon setCodecPreferences #418
Conversation
On Chrome 96, using setCodecPreferences in the way that we do causes the browser to fail on setLocalDescription, even for the offer that it had created.
🦋 Changeset detectedLatest commit: af7fb42 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Failure on the offer it original created even without munged sdp? that's weird.
We can rely on server-side preference. |
Yeah it was strange. I disabled munging and it was still failing with the exact same error. The error also cannot be caught. |
…kit#418) * Fix issue with older browsers erroring upon setCodecPreferences On Chrome 96, using setCodecPreferences in the way that we do causes the browser to fail on setLocalDescription, even for the offer that it had created. * changeset
On Chrome 96, using setCodecPreferences in the way that we do causes
the browser to fail on setLocalDescription, even for the offer that it
had created.
@cnderrauber With the latest version of the server, can we can fully rely on server-side setCodecPreferences? If so we could deprecate this on the client-side.