-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Meet: Unable to Join Meeting #2495
Comments
And today it appears to be working again. |
@2bithacker I am able to join the meeting, but the same problem occurs when trying to share screen. Maybe we could rewrite the issue to address this issue? |
I'm having a similar issue I think? It's hangouts related I believe. I usually make and receive calls from my gmail tab. I just switched to brave a couple days ago. Someone called, and I could see the phone modal pop up, but I couldn't click answer. This seems similar to this issue: brave/browser-laptop#12113 Not sure if I'm crashing this issue, or if I should go make another issue. Let me know if the latter. |
Does lowering shields help? @bsclifton @jonathansampson @rebron can we triage these and dedup? Thanks. |
Related: no audio in Google Meet (work-around is to allow autoplay): |
Duplicate of #4621 and fixed in 1.4.96, a few versions ago. Sharing a screen shouldn't be an issue now either. |
Description
Unable to join meetings on Google Meet (aka Hangouts)
Steps to Reproduce
Actual result:
Browser displays an "Aw, Snap! Something went wrong while displaying this webpage." error.
Expected result:
Browser should display the meeting.
Reproduces how often:
Easily reproduced. Just started happening to me today, was able to join a meeting on Monday without a problem.
Brave version (brave://version info)
Brave: 0.57.18 Chromium: 71.0.3578.80 (Official Build) (64-bit)
Revision: 2ac50e7249fbd55e6f517a28131605c9fb9fe897-refs/branch-heads/3578@{#860}
OS: Linux
Reproducible on current release:
Website problems only:
Additional Information
The text was updated successfully, but these errors were encountered: