Not leading to an information loss; but, potentially, could lead to a loss of vault access.
The truth is that I have the feeling that, in recent months, the quality of Bitwarden’s software has declined considerably.
Add to that the new browser extension redesign fiasco. It doesn’t give me peace of mind.
EDIT: in my opinion, what is most worrisome about that browser extension redesign is not the rejection it caused, but the fact that the new browser extension is plagued with bugs and regressions, all over the place.
I do agree with the experience of buggy releases. For example, I think the Android Refresh would have gone swimmingly well without the newly introduced / regressed bugs. Instead, we are having a portion of the entire userbase having to live with the bugs.
Consider putting more resources into QA, or having a longer beta/rollout periods ignoring the complaints of the users who can’t wait; there are going to be fewer of those compared to the entire userbase complaining/filing about the bugs.
I would add this bug also (though it seems only to be relevant for login items with only the TOTP seed code - i.e. without username and password - stored in them, but if you copy & paste your TOTP seed code somewhere unwanted, that could be also pretty serious):
PS: @grb If you deem that also “serious” enough, you may add that to your original post.
About an hour ago, a maintenance window completed. Now, my “server version” (visible in settings >> about >> about bitwarden) is 2025.4.1. I just tried attaching three (dummy) files to a vault entry, saving/reopening the entry and then deleting the “middle” attachment. The other two remained.
As a result of the upgrade, it might be worth checking if the issue still exists for you.
Ran across a redditor reporting that attachment loss upon reordering affects his company vault, but not his personal vault. Unknown if software/servers were held steady between his tests and don’t know how this detail helps most of us, but I thought it a significant observation.
New bugs always appear in any actively developed project, and Bitwarden is no exception. Developers are currently hard at work to diagnose and fix these issues; evidently, a fix for the URL reordering issue is already pending.
I decide to post the “PSA” topic because the two issues that I called out have the potential to cause loss of valuable data or customized configurations, and because it is possible for users to avoid this risk by simply avoiding certain actions until the fixes are released.
I don’t necessarily think that this pair of bugs should be taken as a symptom of any larger issue.
Well, a nice and good example why I asked the question above is this “bug”:
It is about the URI match detection menu (MacOS and iOS). Small “bugs”, not even bugs. But is it really not possible to change or fix it for one year?
Well, this is my impression that the development is very slow (I have no problem with it - if it makes sense) and the main focus lies on other aspects. But is it not possible for the translation team for German to fix this (btw. there are some more translations which are not so good) or for a developer just to swap the two entries?
There are other important aspects like moving items in an archive (many users ask for this, for many years), or tags. We also read that it is in development, some days ago even a short video of “achieving” an item appeared …
… but it is not mentioned on the Roadmap. It is such an important function; many users ask for it.
It feels a little bit like Apple and the development of the MacOS (and iOS) - many smaller bugs, mostly not really problematic but it is not “perfect” (as Apple would like us to see it). Instead of fixing bugs, we get a few new functions which are also not free from bugs. But to see that many bug are known and exist for a long time, it shows that there is a different focus or no real interest in what users complain about.
The UX of Bitwarden got a facelifting some time ago, but we still see the “old” face. Yes, other aspects are more important (like security), so I understand that UX is not that important aspect.