-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When connected to Google restricted I can't see my files. #422
Comments
Pardon, bad manipulation . Should be support and not bug. |
Same issue to me too. KeePass portable. |
I think you should do 'save as' - 'save to cloud drive' firstly, then you can see the file from 'Open'. |
Same issue, I open a new post with the "bug" template fullfil |
Your comment is valid, it is working like that... to synchronize multi-laptop / tablet & smartphone... It will not be easy |
This happens when you are using Google Drive (restricted) account type: In the restricted mode, KeeAnywhere can run with lower permissions to your Google Drive account, which is usually a good idea for security. But it means KeeAnywhere cannot see any files that were not created in KeeAnywhere. This is why indam's 'save as' trick works. KeeAnywhere has created the file, so permission checks are satisfied. Additionally, KeeAnywhere does not have a "new folder" button to create folders in your Google Drive. It didn't really need one before this. But now, these two facts mean that you can only have your database in the root of your Google Drive. See #398 where the restricted mode was requested. If you need full access, you would use Google Drive account type. But because of another bug (Google's fault), it is not working. There is a workaround for full access if you already were using KeeAnywhere with Google Drive before Google made their change, but it does not work for new users. |
Yes, so I sync the db file manually now. |
The connection to Google restricted checks ok in the configuration of KeeAnywhere, but when I try to open the file the there is nothing in the screen.
The kdbx file is the the root of my google account. Should it be somewhere else? What am I missing?
The text was updated successfully, but these errors were encountered: