[GH-ISSUE #447] WebSocket notifications and attachments #268

New issue

Closed

opened 2026-03-03 01:27:27 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 01:27:27 +03:00

Owner

Originally created by @cybis on GitHub (Mar 31, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/447

Hi,

I've set up the WebSocket notifications accoring to the wiki page and the instant sync between web vault, dekstop applications and browser extensions basically works. So when creating new entries or modifying existing ones, all the clients (except of mobile clients due to the missing push notification feature) get updated. However, when adding attachments to an entry (a secure note for instance) the entry doesn't get updated. A manual sync on all clients is necessary.

Is this the expected behaviour?

BR CyBiS

Originally created by @cybis on GitHub (Mar 31, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/447 Hi, I've set up the WebSocket notifications accoring to the [wiki page](https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-WebSocket-notifications) and the instant sync between web vault, dekstop applications and browser extensions basically works. So when creating new entries or modifying existing ones, all the clients (except of mobile clients due to the missing push notification feature) get updated. However, when adding attachments to an entry (a secure note for instance) the entry doesn't get updated. A manual sync on all clients is necessary. Is this the expected behaviour? BR CyBiS

kerem

2026-03-03 01:27:27 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 01:27:28 +03:00

Author

Owner

@dani-garcia commented on GitHub (Mar 31, 2019):

Uploading attachments should send a notification to the other clients that the entry was updated, same as updating the entry fields itself would do. I'll have to check if I can reproduce this and what might be causing it.

@dani-garcia commented on GitHub (Mar 31, 2019): Uploading attachments should send a notification to the other clients that the entry was updated, same as updating the entry fields itself would do. I'll have to check if I can reproduce this and what might be causing it.

kerem commented

2026-03-03 01:27:28 +03:00

Author

Owner

@cybis commented on GitHub (Apr 1, 2019):

I repeated the test and it seems that the sync is not working only when the attachment is added/modified via the web vault.

When adding/modifying attachments via the desktop app or the browser extension, it works as expected, i.e. all clients (including the web vault) are synced automatically and show the change immediately.

@cybis commented on GitHub (Apr 1, 2019): I repeated the test and it seems that the sync is not working only when the attachment is added/modified via the web vault. When adding/modifying attachments via the desktop app or the browser extension, it works as expected, i.e. all clients (including the web vault) are synced automatically and show the change immediately.

kerem commented

2026-03-03 01:27:28 +03:00

Author

Owner

@cybis commented on GitHub (Apr 14, 2019):

Is this bug specific to the bitwarden_rs implementation or is it also an issue in the original implementation?

@cybis commented on GitHub (Apr 14, 2019): Is this bug specific to the `bitwarden_rs` implementation or is it also an issue in the original implementation?

kerem commented

2026-03-03 01:27:28 +03:00

Author

Owner

@cybis commented on GitHub (Jun 15, 2019):

Issue not observed anymore with latest release (v1.9.1-fff72889).

@cybis commented on GitHub (Jun 15, 2019): Issue not observed anymore with latest release (v1.9.1-fff72889).

kerem referenced this issue

2026-03-03 08:36:31 +03:00

[PR #268] [MERGED] fix bad path in Alpine Dockerfile #2690