Skip to content
Discussion options

You must be logged in to vote

I can confirm a bug fixed where we save tokens in the login keychain without a specific username and thus re-use the saved tokens when opening a new connection. We will have a fix with #17776 to restore support for multiple accounts in the next update.

As a workaround after setting up a connection, delete the tokens saved in the login keychain accessible from Keychain Access.app that have no username set in the item Account name. You will find these by filtering the list by accounts.google.com.

Replies: 2 comments 3 replies

Comment options

You must be logged in to vote
1 reply
@isadon
Comment options

Comment options

You must be logged in to vote
2 replies
@zauqme
Comment options

@dkocher
Comment options

Answer selected by dkocher
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
5 participants
Converted from issue

This discussion was converted from issue #17728 on December 09, 2025 12:34.