You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After starting a chat with a known contact, the verification seal is displayed in front of the sent messages on all devices, regardless of whether DC is active there.
Actual behavior:
After starting a chat with a known contact, the verification seal is displayed first and then the sent message. If DC is currently active on the second device, the seal appears before the message too. But if DC is not active there it will later show the seal after the messages.
Steps to reproduce the problem:
Set up a DC profile on two devices
Close DC on one device; DC-Android must not be active in the background
Start a new chat with a known contact on the other device.
After starting DC on the second device, the seal will be displayed after the messages.
This is a minor bug, but it may confuse inexperienced users and make them believe that their messages were not encrypted.
Also @gerryfrancis reports that after restoring a backup "The chronological order is compromised by receiving a verification message ("messages are encrypted from now on") with the wrong (current) date (at download), not with the initial date of sending."
We can backdate the huge green checkmark message at the time it appears so it has different displayed date of Jan 14 but have sort timestamp of Jan 21, that would work.
Expected behavior:
After starting a chat with a known contact, the verification seal is displayed in front of the sent messages on all devices, regardless of whether DC is active there.
Actual behavior:
After starting a chat with a known contact, the verification seal is displayed first and then the sent message. If DC is currently active on the second device, the seal appears before the message too. But if DC is not active there it will later show the seal after the messages.
Steps to reproduce the problem:
This is a minor bug, but it may confuse inexperienced users and make them believe that their messages were not encrypted.
DC-Android 1.46.14
DC-iOS 1.46.10
DC-Desktop 1.46.8
The text was updated successfully, but these errors were encountered: