Unfortunately, this is a limitation of working via iOS Files interface.Ī quick workaround is to open FE File Explorer settings and tap 'Clear Cache'. All it can do is to show the modification time of the actual file being opened.

If file provider returns an outdated cached copy, KeePassium does not have any means to detect or fix this. I guess this has something to do with iOS limitations on background processes, but this is just an assumption.įrom KeePassium's side it is impossible to force-update the file - this is the responsibility of the file provider app, and it is supposed to 'just work' automatically. The caveat is that keeping the cached copy fresh seems complicated and quite a few sync apps fail to do that properly. So other apps can quickly work with the cached copy, and the file provider would then sync the file as needed. Other file providers handle this better and keep a local cache of frequently accessed files. However, the speed of file operations completely depends on the network connection. (For example, iOS' native SMB integration seems to do that.) This ensures the file is always fresh. Some file providers simply relay all the calls directly to the server. When KeePassium opens this file, the system invokes the responsible file provider module (app extension) which is responsible for actually delivering the data. When you link a database to KeePassium, for the app this is just a file that can be accessed in a standard way. I guess that's why they have a 'Clear Cache' button in the settings. Unfortunately, this seems to happen with some file provider apps.

It looks like FE FileExplorer gave KeePassium a cached file, but forgot about updating it.

Keepassium review