If the storage app fails to sync in background (a common issue with NextCloud app), I cannot do anything about it. KeePassium's sync is completely defined by the third-party app it uses. (KeePassium asks Nutstore to provide the latest data, and uses whatever is returned by Nutstore.) On the other hand, you tested KeePassium, which delegates all synchronization to the Nutstore app. On one hand, you tested Strongbox' built-in WebDAV sync: the app itself directly connects to the server and downloads the data. I use it directly through its built-in WebDAV option. The same way, the same database, so you can judge this is definitely not an iOS problem. As far as I know, the current similar password management APP supports the use of biometric unlocking instead of keyboard. Of course, if you can solve this problem perfectly, it is best because the keyboard is used to manually input complex passwords, and the passwords may be wrong and inefficient. Because I like this app, I started using the beta version, so I hope it can do better. I understand that you as a developer often have limited time. So it's not very high in the priority list. As for #34, it is not a trivial 5-minute task and so far it has been requested by one person only. Most frequently requested features have higher priority. My time is limited, so I have to prioritise KeePassium development. I think that as a password management software, if the synchronization efficiency is not high, it will cause trouble in multi-end synchronization, because manual refresh can not be solved, let alone automatic synchronization in the background. Did you use that option, or added the database via Files? Strongbox has built-in support for WebDAV.
0 Comments
Leave a Reply. |