keepass2android icon indicating copy to clipboard operation
keepass2android copied to clipboard

[BUG] "Failed Requirement" on opening db from Proton Drive

Open kyspykes opened this issue 8 months ago • 3 comments

Checks

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

Describe the bug you encountered:

In the past few days I've been unable to open my kdbx from my Proton Drive. When I try to open the file, either the app crashes/auto-closes or throws an error message saying "Failed Requirement". The same file works when I tested via Google Drive. I've tried 1.11-r0 and v1.12.-r5 but still the same issue.

Describe what you expected to happen:

The database from Proton Drive opens and syncs as normal

What version of Keepass2Android are you using?

v1.12.-r5

Which version of Android are you on?

15

kyspykes avatar May 17 '25 00:05 kyspykes

Does Proton Drive support Storage Access Framework? Note that Google Drive has a built-in implementation which works totally different. Please see https://github.com/PhilippC/keepass2android/wiki/Keepass2Android-file-handling for background information on file access.

PhilippC avatar May 20 '25 07:05 PhilippC

Hi PhilippC,

Thanks for the reply.

I've checked and it looks like Proton does support SAF - the drive shows up in Android file picker and I can select the file which shows in K2A as content://*.kbdx. The issue is that I can't unlock the file for whatever reason; when I enter master password the app either force closes(always on first unlock attempt) and then shows "Failed requirement" when I restart the app and try to unlock again until I try to select the file from android picker again where K2A force closes etc.

Unfortunately I don't know enough about SAF to comment if Proton Vs Google implementation is causing the issue.

Regards,

KY

kyspykes avatar May 20 '25 09:05 kyspykes

(related: https://github.com/PhilippC/keepass2android/issues/2313)

PhilippC avatar May 27 '25 06:05 PhilippC