Page Loader
Weird 'reply' bug detected on WhatsApp: Details here

Weird 'reply' bug detected on WhatsApp: Details here

Feb 02, 2019
12:14 pm

What's the story

WhatsApp has been marred by a weird 'reply' bug, one that is automatically adding reply context for already replied messages in the text box. The issue has been flagged on the beta version of the app and confirmed by multiple users of the messaging platform. It affects the experience of the service, but won't probably slip into the stable release. Here's more about it.

Issue

How WhatsApp is reproducing old reply contexts?

The issue, first reported by WhatsApp tipster WABetaInfo, triggered when you reply to a message - by swiping or long-pressing - and exit a conversation. After this when you return to the same chat, the reply context from the already sent message shows up automatically in the text box of the service - even when you have not chosen that message to reply to.

Problem

Now, this is pretty annoying

While the bug is nothing major, seeing old reply contexts in group or individual chat textbox can definitely prove pretty annoying. Not to mention, if you are in a hurry, you may send a message by quoting as a reply to a previous message from the sender. This may create a discrepancy between what you're saying and what the recipient ends up understanding.

Beta issue

However, it won't probably appear in WhatsApp's stable release

That said, it is also important to note that the problem has been flagged only on the beta version 2.19.27 of WhatsApp for Android. It is neither present on iOS nor on the stable Android version of the app. If you're on this beta version, it is recommended to update the app to a newer version, which should probably fix it.

Previous issue

Previously, WhatsApp deleted message histories

Problems like this can show up on beta releases, but this isn't the only problem WhatsApp has encountered of late. To recall, just a couple of weeks back, the messaging app was found to be deleting old message histories for users. The company acknowledged the matter and claimed an update would fix it soon.