Skip to content
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

Open
artiemart opened this issue Aug 5, 2024 · 7 comments
Open

When connected to Google restricted I can't see my files. #422

artiemart opened this issue Aug 5, 2024 · 7 comments
Labels

Comments

@artiemart
Copy link

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?

image

  • Windows 10
  • KeePass-Version: 2.57
  • KeeAnywhere-Version: 2.1
@artiemart artiemart added the bug label Aug 5, 2024
@artiemart artiemart reopened this Aug 5, 2024
@artiemart
Copy link
Author

artiemart commented Aug 5, 2024

Pardon, bad manipulation . Should be support and not bug.

@artiemart artiemart reopened this Aug 5, 2024
@JustinDScripts
Copy link

Same issue to me too. KeePass portable.

@indam
Copy link

indam commented Aug 12, 2024

I think you should do 'save as' - 'save to cloud drive' firstly, then you can see the file from 'Open'.
But I am wondering if there is a way to specify the path where to keep the .kdbx file in google drive. Not find yet.

@Jigoronico
Copy link

Same issue, I open a new post with the "bug" template fullfil

@Jigoronico
Copy link

I think you should do 'save as' - 'save to cloud drive' firstly, then you can see the file from 'Open'. But I am wondering if there is a way to specify the path where to keep the .kdbx file in google drive. Not find yet.

Your comment is valid, it is working like that... to synchronize multi-laptop / tablet & smartphone... It will not be easy

@Jackabomb
Copy link
Contributor

This happens when you are using Google Drive (restricted) account type:
image

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.

@indam
Copy link

indam commented Sep 14, 2024

I think you should do 'save as' - 'save to cloud drive' firstly, then you can see the file from 'Open'. But I am wondering if there is a way to specify the path where to keep the .kdbx file in google drive. Not find yet.

Your comment is valid, it is working like that... to synchronize multi-laptop / tablet & smartphone... It will not be easy

Yes, so I sync the db file manually now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants