Skip to content

Releases: signalapp/Signal-Desktop

v0.42.4

14 Aug 19:30
v0.42.4
dd8e20b
Compare
Choose a tag to compare
  • Fix for incorrect received_date when downloading large amount of messages from the server.

v0.42.2

12 Aug 20:31
v0.42.2
4c7b174
Compare
Choose a tag to compare
  • When loading a conversation, do check for old messages hidden due to a not-yet-approved safety number and attempt to decrypt them
  • When processing queued messages or retrying incoming messages, maintain original received date
  • Fixed an issue where the security checks before sending to a group with an unknown contact could fail, blocking send
  • Improve performance of security checks before send to groups
  • We now disable the message composition text box when doing security checks before send

v0.42.1

08 Aug 22:10
v0.42.1
50927c0
Compare
Choose a tag to compare

Notable changes:

Application loading screen: We now properly process read receipts, delivery receipts and other types of sync messages before dismissing the screen.

Fix: Properly report decryption errors when they happen

Fix: Slow down expiring message processing, especially on startup (may result in lower CPU/memory usage)

v0.42.0

07 Aug 23:39
v0.42.0
3842340
Compare
Choose a tag to compare

Verified contacts:

  • Ability to verify a contact's safety number, same for group's members via the 'Show members' screen
  • Check mark next to verified contacts, and next to 100%-verified groups
  • Synchronization of verification decisions across devices
  • Banner and confirmation on send when previously-verified safety number changes
  • Confirmation on send if safety number has changed very recently
  • Updated message detail screen when a message fails due to a safety number change

Delete individual message from message detail screen

Clearer error text when a message to a group partially fails

Icons for in-conversation timer change and key change notifications

We now drop duplicate messages when we receive them

A number of reliability fixes:

  • New 'unprocessed' cache for messages not yet fully processed, attempted re-process on startup
  • Protections against 'wedged' conversations, which won't receive or send messages until restart
  • Better resilience to errors throughout the codebase

Application loading screen until server backlog is fully processed:

  • Shows messages processed so far
  • Prevents large numbers of notifications from firing on application startup

Conversation loading screen

Unloading of conversations and old messages due to inactivity to reduce memory usage

Potential fix for "Too many message keys for chain" (caused after desktop is offline for long time)