Desktop client shows old state after saving changes

[benjamin-shen]

Steps To Reproduce

1. Create a secure note with some initial content
2. Edit the item with different content
3. Save the item

Expected Result

The client shows the new state immediately after saving

Actual Result

The client shows the old state until after the user navigates away and back

Screenshots or Videos

https://github.com/user-attachments/assets/d337313b-7b2e-46fd-9f03-b30dfc4f6470

Additional Context

I was able to reproduce with different item types.

Operating System

macOS

Operating System Version

Version 15.1 (24B83)

Installation method

Mac App Store

Build Version

Version 2024.11.0 (33157)

Issue Tracking Info

• [X] I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system. ID: PM-14972

[SergeantConfused]

Hello @benjamin-shen,

Thank you for your report. I was able to reproduce this behaviour and have flagged it to the Engineering department. Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

Thank you again,

[bwbug]

@SergeantConfused I have found an issue that I believe may be related (and could possibly help with diagnosing the cause of #12022):

If you save vault item changes using a different client (e.g., a browser extension), then the WebSockets live sync apparently will push the old/cached state of the modified item to the Desktop app instead of pushing the new state. For example, change the name of a vault item to Revision1 in a browser extension, and observe that the change is not pushed to the Desktop app; then (without doing anything to manually sync the Desktop app) change the item name to Revision2 in the browser extension, and observe that the live sync now pushes the prior Revision1 change to the Desktop app (instead of Revision2 as expected).

If you believe that my observations are unrelated, please let me know, so that I can open a separate issue.