Google Drive (restricted) not display directories on DRIVE

[Flymorox]

used : KeeAnywhere-2.1.0.plgx / KeePass 2.57.1 / x64 W7
Since new GG security method use cloud GG in restricted but when open CLOUD file GG account not display directories... only possibility to move .kdbx file on root GG DRIVE to see :(

[Jackabomb]

This is an intentional limitation of restricted mode. KeeAnywhere is restricted to only be able to see items KeeAnywhere itself created.

It can't see any of your folders because it didn't create those folders. Some other app made them, most likely the Google drive web UI.

[Flymorox]

Ok but this constraint reduces the utility of the plug-in. Is a corrective development foreseen to return to a normal GG mode?

[Jackabomb]

Oh, I agree! It's terrible, there's just not much we can do about it. I do think the maintainer (Kyrodan) is working on it with Google. Issue 398 and 393 catalog the initial discovery of this problem, which prompted the creation of restricted mode.

To be clear, this is a policy change on Google's end, concerning the broad access permissions to your drive account KeeAnywhere needs. Sadly it's not just some bug or API update we could fix with some code and a PR. Kyrodan's got to get Google to approve the app, and I can only guess what that process is going to entail.

[carbone15]

And isn't it possible to add a create folder button? like this you can create your own folder and work with it on the gdrive.

[ElCucoEnPersona]

A "create folder" option would be really nice, or at least a default folder created by the plugin, for organization.

[zediiiii]

For a new Keepass 2 install, I'm now unable to access ANY files using the KeeAnywhere plugin. The file directory is blank with no navigation options and the database in the root director isn't showing up. I can still access on devices where I installed previously, but not with the new install. I'm using Google for work, and I authenticated correctly. No errors are shown and the check shows a good connection.

[Jackabomb]

@zediiiii

1. Download the database file to your device.
2. Open the local copy of it in KeePass with File -> Open -> Open File dialog.
3. Within KeePass, save the file to your google drive with File -> Save As -> Save to Cloud Drive dialog.
4. Close the database using Ctrl+W or File -> Close button.
5. Re-open the database, this time from Google Drive, with File -> Open -> Open from Cloud Drive. This is the step you are trying to do in your screenshot, but I think you skipped the first steps. The file should show up now.
6. If it works, you can now delete the local copy you downloaded in step 1.

All this is needed because

KeeAnywhere is restricted to only be able to see items KeeAnywhere itself created.

Most people did not create their databases with KeeAnywhere plugin. Usually we start using KeePass with a local file, then we uploaded it later to Google Drive when we needed to share it across devices. In that case, KeeAnywhere is not registered as the creator, Google Drive Web UI is the creator.

[zediiiii]

@zediiiii

1. Download the database file to your device.
2. Open the local copy of it in KeePass with File -> Open -> Open File dialog.
3. Within KeePass, save the file to your google drive with File -> Save As -> Save to Cloud Drive dialog.
4. Close the database using Ctrl+W or File -> Close button.
5. Re-open the database, this time from Google Drive, with File -> Open -> Open from Cloud Drive. This is the step you are trying to do in your screenshot, but I think you skipped the first steps. The file should show up now.
6. If it works, you can now delete the local copy you downloaded in step 1.

All this is needed because

KeeAnywhere is restricted to only be able to see items KeeAnywhere itself created.

Most people did not create their databases with KeeAnywhere plugin. Usually we start using KeePass with a local file, then we uploaded it later to Google Drive when we needed to share it across devices. In that case, KeeAnywhere is not registered as the creator, Google Drive Web UI is the creator.

That works. I probably assumed I knew what was going on and missed some documentation somewhere since I've been using the plugin for a long time.