Reload current database when the file is changed elsewhere

[jeff-h]

Description I really like the look of the mac version, and played with it in conjunction with KeeWeb, which I use currently, to test its syncing abilities. I opened the same database (stored as a file on my SSD) in both apps.

When I make a change in KeePassium, it is reflected within a second or so in KeeWeb, with no user interaction. However if I make a change in KeeWeb, it never shows in KeePassium*. I can get it to show by closing the database (pressing esc then the back arrow so I can see the databases listing), then going back into the same database.

Is this how it's supposed to work?

* I know this isn't a fault with KeeWeb, as its changes show more-or-less instantly in other apps eg Strongbox.

Environment:

• OS: macOS 12.3
• App Version: 1.31.104

[keepassium]

Hi, sorry for the delay.

Is this how it's supposed to work?

Yes and no.

Yes, this is how the app is implemented — the database loads either automatically on app launch or manually when you select the file. There is no automatic reload whenever the file changes. The reason is that KeePassium started as a mobile app: checking a cloud-based file for changes means additional network traffic and battery consumption. Unlike desktop, both are limited resources.

And no: ideally, macOS version should take advantage of the "unlimited" resources and reload the file automatically. Let's keep this as an enhancement request :)

[jeff-h]

Thanks for the clarification :) I really like KeePassium on macOS; I've researched a significant number of KeePass apps and not found anything else with this quality of UI & macOS integration (love the AutoFill!) as well as multiple database support etc.

That said, it does show its iOS roots and it would be awesome to see it even more macOS-friendly.

Of all the features in all the clients I've tested, the issue of change handling is the most significant one that several other clients do really well, foremost being KeeWeb in my experience (used it for about a year until now with databases shared via webdav). Multiple people can use the same database, shared via any file syncing method or webdav, and anyone can freely update any entry with it showing up very quickly everywhere.