Selecting 'Google Drive' in 'Manage Databases' does not work.

[rahulgarg123]

Enable 'Google Drive' in 'Manage Database' and click 'Allow' when Chrome requests permission. Nothing happens after that with an error saying [Object object] next to Google Drive (See attachment). Dropbox seems to work flawlessly. Dev console does not show any errors.

[dluzak]

I also have similar issue. I am able to give the permissions to Google Drive, but after giving the permissions I can't see any form for choosing the database file.
I use Chromium version 71.0.3578.98 and Tusk version 2018.9.27.

[gamedevsam]

Same here, I'm using Brave Browser Version 0.59.34 Chromium: 72.0.3626.81 (Official Build) (64-bit)

[joshcangit]

I found out why it won't work. The file isn't named with the .kdbx file extension.

[GrandAlf]

Same here with Brave Browser Version 0.59.34 Chromium: 72.0.3626.81
Tusk version 2018.9.27
It seems like the communication with Google Drive doesn't happen at all, there is no prompt for login

[kalman9]

I too am having this issue. Would love to give this extension a try, but will have to look elsewhere if it can't interface with Chrome (version: 72.0.3626.109)

[esdmr]

(Possibly one way of) Steps to reproduce:
0. Make sure you remove the google Auth-Token from Tusk first.

1. Disable Chrome sign-in (Sync) (Also relaunch chrome to apply settings)
2. Try to authenticate in Tusk
   Expected:
   App falls back to pop-up login.
   Unexpected:
   App fails to authenticate and instead shows [Object object].

Running chrome.identity.getAuthToken() Throws:
Unchecked runtime.lastError: The user turned off browser signin

Tested on Chrome: 72.0.3626.121, Tusk: 2018.9.27

[DeveloperDan]

Having the same issue. The problem occurs on one laptop and not on others. Could the problem be related to multiple google logins confusing tusk?

[nightflyerkilo]

I started having this problem on my Chromebook after enabling 2-step authentication on my Google account. I disabled 2-step authentication and then signed out of the Chromebook and signed back in, and then Tusk was able to talk to Google Drive again. I then re-enabled 2-step authentication, signed out, and signed back in again, and it continued working. So I'm not sure which of those two steps actually fixed it, but I suspect that my Chromebook had just not been properly signed in since I first enabled 2-step authentication.

[bhgsbatista]

This is fixed for me on my work PC (I only have one gmail user there). It is likely related to having multiple GUsers logged into the same browser.

[UndarkAido]

@bhgsbatista In Brave? I'm still getting the issue and I'm only signed in to 1 account.

[bhgsbatista]

I should note I've switched from Tusk to KeePassHelper which uses the KeePassHTTP plugin to fetch passwords from KeePass running on your desktop. This setup works for me since I've always had KeePass open to add / update entries since Tusk didn't have write capacity.

[subdavis]

I've actually ditched Keepass completely.

What once seemed to me like a cohesive ecosystem of supported apps now feels like a precarious wasteland of half-assed attempts all moving in vaguely different directions.

Tusk was a decent attempt, but the Keepass ecosystem overall is too many things to too many people. I'd love to drop support for Google, OneDrive, and OwnCloud all together and have it be a dedicated Dropbox read-only helper.

I've switched to Password Store (git + gpg + bash) and I'm much happier now.

Since I no longer use Tusk myself, I think I should either archive it or find someone dedicated to keeping the project alive.

In general KeePassHTTP is a saner and more secure way to get passwords into your browser.

[UndarkAido]

M'kay, I'll give some of the KeePassHTTP plugins a try, I never really liked in in the past though and I doubt they'll function from Wine on my work Mac.

Thank you for Tusk while it lasted! Made Keepass a whole lot better.

[joshcangit]

This is no longer a bug but it's still present as a glitch. This does seem related to issue #133. It temporarily goes away after being signed in and having KeePass Tusk been authorized then re-opening the KeePass Tusk settings page.