You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
I use a password + key file for authentication and a key database in a goggle drive to share it among devices. For safety reasons I put the key file in the internal storage.
The key database on gdrive is not the master key database for various reason so I happen to update it when needed. To use the new version, I have to click on change database. I select the database in gdrive but then I have to configure again password and key file. The problem is that I cannot access the key file again.
Describe what you expected to happen:
I would exepect the applications propose to browse the location where it store the keys as it cannot be accessed by other apps for security reasons.
What version of Keepass2Android are you using?
1.10-pre
Which version of Android are you on?
Android 14
The text was updated successfully, but these errors were encountered:
Checks
Describe the bug you encountered:
I use a password + key file for authentication and a key database in a goggle drive to share it among devices. For safety reasons I put the key file in the internal storage.
The key database on gdrive is not the master key database for various reason so I happen to update it when needed. To use the new version, I have to click on change database. I select the database in gdrive but then I have to configure again password and key file. The problem is that I cannot access the key file again.
Describe what you expected to happen:
I would exepect the applications propose to browse the location where it store the keys as it cannot be accessed by other apps for security reasons.
What version of Keepass2Android are you using?
1.10-pre
Which version of Android are you on?
Android 14
The text was updated successfully, but these errors were encountered: