This issue is a
Please describe the current behavior, and explain why it's bad.
When using a database stored on Google Drive, Tusk periodically looses its Google authentication data. This manifests when trying to unlock the database: After entering the database password, Tusk reports and error that "User interaction required." (If you have quick eyes, you can sometimes see the authentication UI start to open and then immediately close right before this error appears.) Switching to the settings, Google Drive will momentarily show up as busy, and then change to disabled with the same error message.
Re-enabling Google Drive works fine, after which the database stored there can be opened normally... At least until the next time that Tusk forget the Google login information.
It's hard to tell how long it takes for login information to be forgotten, but after some testing it appears to happen within ~30 minutes of when the database password itself expires. I've tried explicitly allowing both cookies and popups for Tusk, but to no avail. Perhaps the Google Drive authentication data is being cleared with the database password?
This issue occurs on a Chromebook when pulling a database off (G Suite) Google Drive (I'm testing right now to see if it's feasible to roll Tusk out to end-users at my work); other operating systems and storage mechanisms have not been tested.
Please describe how you think it should change.
Preferred: Tusk should remember login information for Google Drive indefinitely (even if it forgets the database password).
Second Best: Tusk should correctly display a re-authentication prompt for Google Drive when it looses those credentials, rather than forcing the user to open up its settings and manually re-enabling Google Drive.