[deleted] Is your "export" file just a .kbdx
file? If not, please copy the correct file, as KeePass apps only use that file to store all the passwords and notes.
The send.vis.ee repository seems to be active, as its latest commit is (at the time of writing this) 5 days ago, and the maintainer is still responding to issues. You can always try other forks or similar services if you don't feel confident using a particular one.
The problem with all your issue seems to be that you don't import the file in your local storage. I can't explain why, because I don't know any better, but I think there are problems if you try to read encrypted files from an external storage as per GrapheneOS' handling of files. The immediate solution that's quite certain to work is to copy the keepass file onto your device's storage, and let keepass access it from there, instead of trying to access it from the USB.
If you wanted to have the file on the USB stick because you want to always have an up-to-date version, I shall recommend you do one of these instead:
- if your
.kbdx
file is essentially stable, e.g. if you don't add/remove many password or make many modifications in a month/year, you can use the USB stick to manually transfer the file every time you make a modification, since there won't be many time you'll have to do this
- if you want to have is automatically synced every time with your devices, but don't want to trust a cloud service, you could use Syncthing. It works flawlessly, and this is the way I use it.
If you instead want to have the .kbdx
file solely on the USB stick because you don't trust your Pixel's local storage or any cloud provider, please reevaluate your belief. GrapheneOS' storage, and Android's security model in general, built on Android's file-based encrypted storage, with the encryption keys securely stored on the device's Titan chip (a secure element) is by far the most secure storage you've ever encountered and at your disposal. Again, security is practically the whole purpose of GrapheneOS. A simple USB stick is not even encrypted, and if you use the proprietary Sandisk encryption you are shooting yourself in the foot.