v2.5.2
Newly added Google Meet logins can sign in
- 1improved
- 1fixed
A Google Meet login added to an existing workspace failed to sign in on every run and silently joined anonymously, while older logins on the same workspace kept working. Setup failures now also name their actual cause instead of timing out generically.
Improvements
- A failed Meet sign-in reports what is wrong — the wrong Workspace domain, an SSO profile not assigned to the user's organisational unit or group, or an unfinished "Welcome to Google Workspace" flow — instead of a 45-second timeout with no detail. See Authenticated bots for Meet.
Bug Fixes
- A newly added Meet login now signs in on its first bot. Previously every run fell back to an anonymous join and ended as
BOT_NOT_ACCEPTED, which pointed at the meeting host rather than at the credential.