When sending an attachment, it misleads the sender: the checkmark indicating successful delivery to the server appears immediately. Apparently, the attachment’s text part is delivered to the server first, and the client interprets this as successfully delivered — even when the attachment text is empty. As a result, the recipient sees a banner saying the video can be downloaded, even though it hasn’t actually been uploaded to the server yet.
This bug appeared in version 2.43, after the issue with an empty message arriving before the attachment was fixed.
Moreover, this happens even when the setting for automatic download of attachments of any size is enabled.
2 Likes
Also, because of this bug, the read receipts for attachments are not displayed when the recipient has viewed them.
1 Like
This is a pretty serious bug. I honestly don’t understand why there’s still no mention of fixing it. Attachments just confuse the hell out of people — you can’t tell whether the file actually arrived or not. It’s completely unclear.
Before, it worked much better: you sent a file, it reached the server, then it downloaded to the recipient’s client and was displayed. Simple and predictable. But now it’s a mess. As soon as you send an attachment, it immediately shows as “delivered,” even though it hasn’t actually been delivered yet.
On the recipient’s side, it shows a prompt asking whether to download the file, even though the settings are configured to automatically download the full size. And in the end, after the recipient reads it, the sender still can’t see the read status.
In short, it’s a nightmare. I have no idea what the developers are looking at, because this is a real problem and it makes the app inconvenient for people to use.