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.