Not working on Chromium 63?
See original GitHub issueFirst of all, thanks for such a great product! We use jitsi meet a lot and we’re loving it.
Recently I have installed Ubuntu 17.10, as well as Firefox and Chromium. I like jitsi better in Chromium since I can share full screen. In the previous installation (I was on Ubuntu 15.10, and Chromium was stuck, outdated at ~53), it was working just fine.
However, on Chromium 63 I’m getting this message:
Console shows the following errors:
[react/features/base/connection/actions.web.js] <>: TypeError: Cannot read property 'isPluginInstalled' of undefined
Uncaught (in promise) TypeError: H.webRTCReady is not a function
(Also the fully supported browsers link is not working)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Chrome browser v 63 not working for chrome web driver v 2.35
Steps to reproduce the problem: Getting this error while running the chrome through the cmd as per instructions of the chromewebdriver expert.
Read more >Chrome 63 has broken workspaces - Google Groups
After updating to v63 my existing workspaces were removed and adding new ones simply does not work. After adding a folder to workspaces...
Read more >Chrome Releases: Stable Channel Update for Desktop
The Chrome team is delighted to announce the promotion of Chrome 63 to the stable channel for Windows, Mac and Linux.
Read more >Cross Browser Compatibility of URLSearchParams in Chrome ...
URLSearchParams is Fully Supported on Chrome 63. Checkout overall cross browser compatibility of URLSearchParams on Chrome 63.
Read more >Media updates in Chrome 63/64
Chrome now pauses all background video-only media. Audio is not muted anymore for extreme playbackRate. # Media Capabilities - Decoding Info API.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, all y’all! Fix confirmed on my end.
Yes, meet.jit.si is now running jitsi-meet 2569 which includes [the fix]https://github.com/jitsi/lib-jitsi-meet/pull/698)