I use this setup for my personal passwords, using nextcloud as the sync solution. A semi-fix for that was using Keepass2Android (on Android obviously). It integrates with nextcloud directly, keep a local DB of passwords, and would only load the remote one (and merge) on unlock and updates, not keeping it “constantly” sync on every remote change. It works well… most of the time… with only two devices that almost always have connection to the server… and for only one user.
It’s overly clunky though. It’s the big advantage of “service based” password manager against “single file based” ones. They handle sync. We have plans to move to bitwarden at my workplace, and since the client supports multiple accounts on multiple servers, I’ll probably move to that for personal stuff too. The convenience is just there, without downside.
It certainly does work, until you look at numbers and they are either negligible, or great until they stop being great quickly.
https://www.mdpi.com/2306-5338/11/10/167 https://www.tandfonline.com/doi/abs/10.1080/00207233.2024.2358707 https://www.jstage.jst.go.jp/article/jmsj/102/4/102_2024-021/_article/-char/ja/
I would not call that a consensus on “it does work”.