You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
Meetbot failing to "sign in to Google" and doesn't work due to this precautionary check by Google shown when signing in.
Workarounds,
We can handle this by clicking the button and signing in when the screen shows "Verify it's you"
OR, we can terminate the running browser session and let meetbot sign in into a new browser instance preferably without cookies or an authentication notice. That what I will do by restarting the container,
The error:
07.03.22 20:28:37 (+0530) main we're already logged in
07.03.22 20:28:37 (+0530) main going to Meet after signing in
07.03.22 20:29:15 (+0530) main Unrecoverable bot error occured: waiting for XPath `//*[contains(text(),'call_end')]|//*[contains(text(),'Join now')]` failed: timeout 30000ms exceeded
07.03.22 20:29:15 (+0530) main Leaving the meeting: https://meet.google.com/yhc-fmfq-hxx
07.03.22 20:29:52 (+0530) main typing out email
07.03.22 20:30:22 (+0530) main Unrecoverable bot error occured: waiting for selector `input[type="email"]` failed: timeout 30000ms exceeded
07.03.22 20:30:22 (+0530) main Leaving the meeting: https://meet.google.com/yhc-fmfq-hxx
07.03.22 20:30:42 (+0530) main typing out email
07.03.22 20:31:12 (+0530) main Unrecoverable bot error occured: waiting for selector `input[type="email"]` failed: timeout 30000ms exceeded
Impact:
Meetbot doesn't work until this is fixed or workarounds are deployed
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Meetbot failing to "sign in to Google" and doesn't work due to this precautionary check by Google shown when signing in.
Workarounds,
The error:
Impact:
Meetbot doesn't work until this is fixed or workarounds are deployed
The text was updated successfully, but these errors were encountered: