Problems with Chrome-based browsers version >= 87

There was an issue in chrome 86 so we fixed it using a patch in browser capabilities.

This patch fixed the issue but today after one month, we are facing same issue on chrome Version 87.0.4280.66 (Official Build) (64-bit).

Please help if any fix is available. Our code base is old hence can’t move to the latest commit.

Error : [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: null Script: null Line: null Column: null StackTrace: Error: Strophe: Error: Failed to execute ‘createEncodedStreams’ on ‘RTCRtpSender’: Encoded audio streams not requested at PC initialization
at a.handleSender (adapter_core.js:15)
at se._setupSenderE2EEForTrack (currentExecutingScript.js:1)
at currentExecutingScript.js:1
at I.Handler.handler (strophe.umd.js:2701)
at I.Handler.run (strophe.umd.js:1854)
at strophe.umd.js:3148
at Object.forEachChild (strophe.umd.js:826)
at I.Connection._dataRecv (strophe.umd.js:3135)
at D.Bosh._onRequestStateChange (strophe.umd.js:5006)
at Object.r.Strophe.log (adapter_core.js:15)
at Object.fatal (strophe.umd.js:1382)
at Object._handleError (strophe.umd.js:1299)
at I.Handler.run (strophe.umd.js:1854)
at strophe.umd.js:3148
at Object.forEachChild (strophe.umd.js:826)
at I.Connection._dataRecv (strophe.umd.js:3135)
at D.Bosh._onRequestStateChange (strophe.umd.js:5006)

@damencho Please help.

1 Like

I’m with Chrome 87 and I’m not seeing any issues when opening meet.jit.si. Which jitsi-meet version do you use?

We are using customized version of jitsi meet from may 2020 commits. So our code base is old. We faced same issue in chrome 86 and got it fixed by applying this commit https://github.com/jitsi/lib-jitsi-meet/commit/cf1305bdd27a412e927d61c21a6e16e8a15a4576

Now the error message is coming same on chrome 87 and working fine on chrome 86.

We have also tried to merge latest branch but facing huge amount of merge conflicts.

I doubt we can’t use latest lib-jitsi-meet with jitsi-meet of may 2020 commit?

No idea about this.

A really-really wild guess without knowing anything around the e2ee can you try applying this to your lib-jitsi-meet and test: https://github.com/jitsi/lib-jitsi-meet/commit/92ea388ce979cd9907676a9da68717d2c87904c6
I just chose it because of the commit message mention that this is due to a change in chrome, so maybe that chromium change from Aug got pushed to Chrome 87.

Thanks for the reply, I will test this fix and will get back to you.

@damencho i tried this fix but the error was same.
Also i tried latest lib-jitsi-meet minified build and luckily it was working with old jitsi-meet (May 2020 commits),

Is it means, that there are no breaking changes in lib-jitsi-meet and that’s why latest minified build is working with old frontend code.?

Probably, yeah we try to keep it that way, but its not guaranteed … Try also screenshare …

Yeah screenshare is working as expected.

We experience the same issue as Amit.
We are in the same situation and we also applied the patch to fix issues with Chrome 86.
Now, all clients that have updated to Chrome 87 receive no video-feed and we get the error messages listed below.
Did you manage to solve this issue @Amit_Singh_Bhandari (or @damencho )?

We get the following logs (send/receive)

In E2EEContext.js:103
Uncaught (in promise) DOMException: Failed to execute ‘createEncodedStreams’ on ‘RTCRtpSender’: Encoded audio streams not requested at PC initialization
at a.handleSender (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:17:26511)
at se._setupSenderE2EEForTrack (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:196499)
at se._setupNewTrack (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:168743)
at https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:167745

In E2EEContext.js:72
Uncaught DOMException: Failed to execute ‘createEncodedStreams’ on ‘RTCRtpReceiver’: Encoded audio streams not requested at PC initialization
at a.handleReceiver (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:17:26177)
at se._setupReceiverE2EEForTrack (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:196852)
at se.onRemoteTrackAdded (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:174607)
at a.emit (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:1:129514)
at A._createRemoteTrack (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:121083)
at A._remoteTrackAdded (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:120628)
at A._remoteStreamAdded (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:118900)
at RTCPeerConnection.A.f.a.usesPlanB.peerconnection.onaddstream (https://app.life-manager.net/assets/libs/lib-jitsi-meet.min.js:10:114767)

Thanks for any assistance
-Lars

You can visit https://github.com/jitsi/lib-jitsi-meet follow the steps to create the minified build.
Then replace your old lib-jitsi-meet.min.js file from your server.

Thanks Amit. This did indeed solve the issue.

1 Like

Hi @Amit_Singh_Bhandari and @Hoegsted , I did not get how exactly you guys solved the issue, can you please explain in more detail?