January 6, 2011 | by Lars Aronsson
Remember that Android text messaging bug that got some users worried late last week? There were two separate issues with the Messaging app, and Google has now acknowledged both of them. The Android developers have been able to reproduce the issues, and found out a way to fix them.
When tapping to open a message, the first bug would sometimes cause another message to be displayed instead. The glitch is apparently more likely to occur if you tap on a message before the Messaging app has completely loaded, so Google recommends that you wait for all the elements to load before using the application.
The second issue is more serious, since it simply would deliver sent messages to the wrong people. You don’t have to have a wild imagination to realize that the consequences could be quite embarrassing and inopportune. Luckily, both bugs seem very rare and fixes will be deployed, but how they will be applied is not mentioned. This is Google’s official response:
“Thanks to everyone for your patience while we’ve been investigating these reports. As it turns out, we believe there are two distinct situations being discussed on this issue chain. Fortunately, we have fixes for both of them.
When some users tap to open a message in the Messaging application, they’re seeing a different message appear instead. We don’t believe this issue is affecting many users, but we’ve developed a fix that we’re preparing to deploy. Of course, double-checking the displayed message before hitting “Send” will prevent any messages from being sent to the wrong recipients. We’ve found in testing this issue, it is more likely to occur if you tap on a message before the Messaging app is fully loaded, so we recommend waiting for all the elements to load before clicking on the message you want to display.
Separately, some users have reported that their SMS messages are being delivered to the wrong people. It took us some time to reproduce this issue, as it appears that it’s only occurring very rarely. Even so, we’ve now managed to both reproduce it and develop a fix that we will deploy.
While we don’t anticipate any persistent problems, we’ll continue to investigate in case we come up with additional ways to trigger these bugs. Thanks again for helping us improve Android.”