Philipp Crocoll

A user of my app (Keepass2Android) had trouble opening the database. It turned out that he thought he has configured the database to use a key file (and tried to open it with the key file), but my app failed to open the file because the database actually did not use/require the key file. He had created the database, then selected Extras > Erweiterte Werkzeuge > Schlüsseldatei erstellen. This seems to create the key file but not add it to the master key. Suggestion: Ask the user if he wants to add...

ok, great! "IfDevice" sounds like a suitable name!

Hi Dominik, thanks for your feedback! I didn't think about the DB_DIR placeholder - that certainly helps in many situations (for KP2A it should work with (S)FTP(S),WebDav,Dropbox,OneDrive and PCloud - hopefully it also work with the KeePass plugins). I think it would not work for GoogleDrive (because KP2A requires the GoogleDrive-ID as part of the path) and local files opened through Android's file browser (their filenames are content-URIs which even do not always even contain the actual filename...

As the author of Keepass2Android, I have recently added support for having several databases open simultaneously (https://github.com/PhilippC/keepass2android/issues/174). I suppose that many users would benefit from having something like KeeAutoExec on Android as well, so I am planning to integrate this in KP2A, too. I am interested in feedback, both from KeePass users and Dominik, about the following thoughts: I don't think that a single AutoOpen entry as it is defined at present will work across...

To answer the original question , the answer is no, you need at least 1.01 pre444...

I have updated the file yesterday to which wellread has linked ,it should now be...

Compiling with Xamarin Android was relatively easy , but required a few code changes...

@mstarke This sounds really interesting, as I was planning to work on a sharing feature...