WebSocket notifications and attachments #3908

New Issue

2026-03-07T19:19:31-06:00

GiteaMirror commented

2026-03-07 19:19:31 -06:00

Originally created by @cybis on GitHub (Mar 31, 2019).

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). 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

GiteaMirror added the bug label 2026-03-07 19:19:31 -06:00

GiteaMirror closed this issue

2026-03-07 19:19:32 -06:00

GiteaMirror commented

2026-03-07 19:19:32 -06:00

@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.

GiteaMirror commented

2026-03-07 19:19:32 -06:00

@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.

GiteaMirror commented

2026-03-07 19:19:33 -06:00

@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?

GiteaMirror commented

2026-03-07 19:19:33 -06:00

@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).