-
Notifications
You must be signed in to change notification settings - Fork 178
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
Bug: Cannot join or create meetings in Google Meet #998
Comments
reproduced on the macos Monterey |
This happens for me as well on macOS Monterey 12.1 |
Same here on KDE Neon 22.04, Ferdium 6.2.3 (Flatpak) |
Tried the approach here and not working either: #611 |
Also seeing the same issue on Fedora 36, RPM package. =================================== |
It seems this bug still exists. I am able to make a call occasionally, but in the majority of the cases, I can't. Is there a plan to fix this? Thanks! (Win10Pro, Ferdium 6.7.3) |
Bump.
Tried changing WebRTC settings like mentioned here #611 (comment) but no avail. What's interesting is that, when I open devtools and navigate through window.location.href to meets, it works well (but well, all the other services disappear as I change from file to web...) |
I can reproduce it as well.
|
For me, if I open the Service Developers Tools before joining a Google meeting, it works. I have no idea why it works, or if it is not really related. But it is a possible workaround. |
Avoid duplicates
Ferdium Version
6.0.0-nightly.98
What Operating System are you using?
Windows
Operating System Version
Windows 10 Pro Version 21H1 (OS Build 19043.1826)
What arch are you using?
x64
Last Known Working Ferdium version
N/A
Expected Behavior
Joining and creating meetings with Google Meet service to function
Actual Behavior
95% of time joining and creating meetings with Google Meet service ends up with an infinite loading screen with the prompt "Joining...".
Strangely using custom web recipe functions (outside of screen-sharing).
Steps to reproduce
Debug link
https://debug.ferdium.org/3c41936e-ca52-4229-8f7b-9171bbc6189d
Screenshots
Additional information
No response
The text was updated successfully, but these errors were encountered: