If a disappearing message expires when Signal is closed, the preview of the message under the chat's name will not disappear until that chat is viewed or clicked on.
Actual result: The first line or so of the "disappeared" will be displayed in the preview box under the chat name until that chat is selected.
Expected result: The preview box would show the last regular message, because the "disappeared" one should already be gone.
Operating System: Ubuntu 16.04 LTS
Browser: Chrome
Signal version: 0.26.0
I can confirm this issue in Chromebook, fwiw. Version 0.26.0. A related issue-- When you do open the full chat window, the old messages appear for a moment before being deleted. An adversary in possession of the computer could, say, video record the screen as it clears and would be able to play it back, freeze frame the screen, and review the last few deleted messages before they were cleaned. It would be preferable if these messages were expired prior to being put on screen, (and ideally even before that, assuming they could be extracted from memory or a cache..)
Also-- a third bug-- in another chat window I noticed only MY messages were being expired and removed, whereas my correspondent's messages, which should have also been wiped out, remained in a vertical stream of one-sided chat bubbles.
Again, this is version 0.26.0.
In my case, the preview of the supposedly "disappeared" message doesn't even disappear when viewing or clicking the conversation. Even exiting and restarting Signal Desktop doesn't change this. The text of the last message - disappearing or not - is shown in the preview not matter what.
This only seems to be true when I'm sending messages to myself (Desktop to Android), though.
v0.27.0
Log for same issue: https://gist.github.com/37df7f6b329879aa15f670887ebdb946
I can confirm this is happening on the Signal Desktop Electron client.
i see it too
+1
I can confirm this happening on the macOS desktop client, v1.6.1
I noticed this on the Linux desktop client, version 1.6.0. I will work on a fix.
The fix for this issue has shipped in Signal Desktop 1.7.1. Please report back here with any new cases of this or open a new issue. Thanks 馃槃
Most helpful comment
I noticed this on the Linux desktop client, version 1.6.0. I will work on a fix.