Keepass won't open the database; I have to find the database and tap it

SteveC

This is annoying.

If I select the keepass icon and try to open the database, I get:

An error occured: Exception of type "keepass2andriod.Io.DocumentAccessRevokedException' was thrown.

HInt: Keepass2Android has stored the last successfully opened file version on internal storage. You can open it by tapping Change database and selecting the local backup.

Except I can't; it won't let me open the recent databases either. (There's a nearly hidden show backups button that I just now noticed that DOES work--readonly but that's all I usually need. But I shouldn't have to do this, should I?)

However if I go into file manager, back it out of "Downloands" (Is there any way to change this silly default?) and go to the Pixel 8a area, and navigate to the keepass file, and tap on it, keepass has NO PROBLEM opening it. But again, why should I have to do this?

SteveC

An additional note: the backup did not have my most recent entry (which is the one I wanted); so I had to navigate through the file manager anyway.

n3t_admin

is it possible you used storage scopes?
Judging by the logs, Keepass expects full file access to work properly.

BeepBeep

I use KeepassDX, which targets Android. Is that what you're on? If not, you may want to try that.

In DX, at the home screen (before login) there's...
Settings - > App Setting -> History -> Remember database locations (turn it on)

If you're not on DX, whatever app you're on may have something similar.

mar2112

BeepBeep I have no issues with DX either.

SteveC

BeepBeep

I'm using KeepPassXC.

The setting you reference seems to be located in a different place in XC: settings->app->security->remember databases and is already turned on.

@"n3t_admin"

As for storage scopes, I have no idea what that even means. The documentation just kind of waved its hands and said such a thing exists but I didn't come out with a sense for whether I wanted to use it or not and have no idea what I'm set to.

If it helps, I am not doing this through the owner account but rather through an account named "me". (I hope this isn't another one of those things that only works from the owner account--like blocking numbers from the phone app is--or I'll have to ask what the point of other accounts is.)

BeepBeep

So far as I know, Keepass XC only runs on Mac, Windows, and Linux.
Not sure you got it installed on Graphene.
For Android/GrapheneOS use Keepass DX.

I'm not sure it's applicable to your issue, but since you asked: Storage Scopes is a memory storage sandbox feature of GrapheneOS. It let's apps think they have full access to your storage to improve compatibility for those apps that don't work properly without it while protecting your privacy from these apps by isolating those apps' own storage area from the rest of the device's storage. Keepass(DX) doesn't need Storage Scopes, but with respect to the comment of @Nn3t_admin , in general if you have an app contained within a Storage Scope it cannot access at all a file (e.g. the Keepass database) if it is located outside the app's own scoped storage space (i.e. in main storage or within another app's scoped storage). Storage Scopes is enabled in the app settings (press and hold the app icon and then select Info).

SteveC

BeepBeep

Thank you for putting in the time to help!

It appears I am using something called Keepass2Android.

XC does indeed run on linux; I was apparently thinking about my Linux box when I wrote I was using it.

With respect to Storage Scopes, from your description (clearer than the docs, where one gets the impression it has something to do with Google Play), I wouldn't be able to open a database file from the file manager if it were outside of the scope. (The file manager does not know it's a Keepass file, it calls it a "bin" file. That may or may not be significant.)

In any case even following your directions for how to get there, I can't find a setting regarding storage scopes.

BeepBeep

SteveC

You don't need Storage Scopes. You also don't want Storage Scopes activated, because you're (presumably) going to want to sync the Keepass database file, which is mostly incompatible with Storage Scopes.

Last I heard (if I'm not confused), Keepass2Android didn't seem to be getting updated anymore, but I just now looked, and apparently it's back in play. In any event, the DX fork works fine. I use XC on Linux and Windows. The databases are interoperable.

https://www.keepassdx.com/

I don't know whether the Google Play Store version has any Google dependencies, but the other 2 sources do not. So, maybe you'd want to avoid the Play Store unless you've also got Google Services Framework running on all relevant profiles, just to remove a potential source for a compatibility problem -- or just try it from Google Play and bear in mind that could be an issue. The general wisdom around here is that if you aren't using the Play Store you're better off going direct to the GitHub repo via Obtainium than using F-Droid, but both work.

SteveC

BeepBeep The databases are interoperable.

They certainly are; I generally just copy whichever one I just added to to my other devices and do a merge, when I add a new password.

Will try DX via Obtanium (I was unaware of Obtainium until now, thank you).