From 3171d356cc170c603494170ec9b715ec45266604 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Calvi=C3=B1o=20S=C3=A1nchez?= Date: Fri, 22 May 2026 10:17:27 +0200 Subject: [PATCH] fix: Refresh all conversations when deleted from one not active in MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When the HPB is used and a user is removed from a conversation that user receives a "disinvite" signaling message. This triggered a "should-refresh-conversations" event, but (unless it coincides with the periodical forced refresh) only those conversations modified since the last fetch will be got. As the deleted conversation is no longer accessible by the user it will not be returned in the "modified since" response, and the conversation list will not be properly updated. Due to that a "disinvite" message for a conversation that the user is not active in should trigger a forced refresh of all the conversations instead of a normal refresh. Signed-off-by: Daniel Calviño Sánchez --- src/utils/signaling.js | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/utils/signaling.js b/src/utils/signaling.js index ee5f48a37e9..51a98bdfdf9 100644 --- a/src/utils/signaling.js +++ b/src/utils/signaling.js @@ -1505,7 +1505,9 @@ Signaling.Standalone.prototype.processRoomListEvent = function(data) { EventBus.emit('deleted-session-detected') break } - // eslint-disable-next-line no-fallthrough + + EventBus.emit('should-refresh-conversations', { all: true }) + break default: console.debug('Room list event', data) EventBus.emit('should-refresh-conversations')