[BUG] Google Drive: this app is blocked

[dekiesel]

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

I am basically encountering the same bug as in #1833 .

It started randomly today on my version of 1.09, which I then updated via the playstore to 1.11 where the problem persists.

I have deinstalled and reinstalled the app, also tried clearing the cache and data.

When I select "Google Drive" i see the Google Drive account selection screen. After clicking on the account that holds my keepass-db I get:

This app is blocked.

This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.

Describe what you expected to happen:

I expect to be able to access my database file via google drive.

What version of Keepass2Android are you using?

1.11-r0

Which version of Android are you on?

12

[martinqc101]

I had the same problem. I found the solution. I checked "Use limited access" like on ma printscreen. Now it work again!

[dekiesel]

Thanks, but that seems to be a windows dialog?

[The-Scout]

That user is fixing the same issue for a plugin for the windows version of keepass 2, I don't think said legacy option exists in the android app, and am having the same issue.

[Havokdan]

From what I've heard, Google is charging a high price for applications to have the access they had before, so to continue using them as easily as before, the developer has to pay the amounts (many won't) or use options and resources like cited by the colleague for the plugin on Windows.

[martinqc101]

From what I've heard, Google is charging a high price for applications to have the access they had before, so to continue using them as easily as before, the developer has to pay the amounts (many won't) or use options and resources like cited by the colleague for the plugin on Windows.

Sorry I read too quickly and you had the same message as me for the android version of KeePass. I have the same version of Keepass2Android but on Android 15 and everything works correctly. Except that after my modifications made in the Windows version I found myself with a duplicate database because a copy was created at the root of my Google Drive. Now my KeePass works normally on both Android and Windows. Before finishing my comment, I just tested with a version of Android 11 and I also managed to synchronize KeePass with my drive account.

[pseudacris]

The developer linked this as a solution for the Android version in a reply to a review on Google Play. But there is no solution for Android here, just Windows.

So what do I do to not be blocked by Google on Android?

[Havokdan]

I think the only alternative is to use the Google drive app.

[badplay]

same problem for me but i found a fix:

Windows See Above that worked for me
for Androd i found in Reddit a Simple Solution:

"As far as I know of Google Drive, Dropbox and any name brand cloud storage. They mount themselves, all that OP needs to do is 'System file picker' and go to the mounted google drive; rather than the 'google drive' tile on K2A."

so we have to setup the drive account on our android device then inside keepass2android go to local android search and then use the linked drive account. for mee i see all my drive on left side of the local file manager

then use your password box file for keepass and all works great

[dekiesel]

then use your password box file for keepass and all works great

That works for one db, but it fails (for me) if you use a child database.

[wenz]

From what I've heard, Google is charging a high price for applications to have the access they had before, so to continue using them as easily as before, the developer has to pay the amounts (many won't) or use options and resources like cited by the colleague for the plugin on Windows.

Sorry I read too quickly and you had the same message as me for the android version of KeePass. I have the same version of Keepass2Android but on Android 15 and everything works correctly. Except that after my modifications made in the Windows version I found myself with a duplicate database because a copy was created at the root of my Google Drive. Now my KeePass works normally on both Android and Windows. Before finishing my comment, I just tested with a version of Android 11 and I also managed to synchronize KeePass with my drive account.

I had a similar phenomenon, hopefully it helps others: I am storing the KeePass database file in a specific folder in GDrive. After changing the sync settings in the Windows KeePass options, a second folder with the same name was created! Had to open that file in the Android app, now synching works again.

[donet]

Dear all,

I was already pointing to the file (without using the Google Drive plugin) but using the Android file selector) what I notice is that the file on the Android device is always opened as content://<file_name>.kdbx no matter of its real path (that was under my GDrive path), when the file is saved is is not saved in the original GDrive location so the version on GDrive is no more in sync with the version on the Android device.

This changed about a month ago (dec 24).

[PhilippC]

Sorry that I haven't been able to fix this yet. I am actively working on the app, but in order to solve the GDrive issue, I first need to update quite a few things such that Google allows to pulblish a new release (apps need to target SDK level 34 which requires a new build system as Xamarin.Android is deprecated). I have managed to do the migration to .net8, but still have some changes to make until the app can be updated again. I will definitely try to solve this as soon as possible. Sorry that "asap" is not as fast as it should be.