Remember back in the day when Apple users use to gloat about how protected their devices were and that they never had issues like Microsoft or Android users do? Those were the good ol’ days, huh? As we have seen with other devices that gain more than half the market share, they instinctively become a target for people that look for exploits that can cause many Apple users inconvenience to downright dead devices. A new bug is causing some people a great deal of pain now.
A new bug is making its way around the iOS and Messages market that will cause some people’s message app to crash when they receive a certain text or when locked it will automatically reboot itself. Now, the issue is not only prone to iPhone-to-iPhone as originally suggested, it will impact iPhone users if the text is sent from an Android device. The news of this bug has been around for a few day and Apple had remained quiet about it.
Fortunately for all iPhone users, it seems that Apple is officially aware of the problem and is working on a fix. “We are aware of an iMessage issue caused by a specific series of unicode characters and we will make a fix available in a software update.”
Now this is not an exploit that people can find by sending you a specific email or someone randomly can cripple your iMessage app, but if you know someone that would like to screw with you then you should be a bit worried. Fortunately, as we wait for Apple to grace us with their update, there are some workarounds you can do if you are affected by an unkind troll.
- If you are friends with the sender, you can ask them to send you another text that will effectively cancel out the initial strain.
- You can send yourself a message via Siri, the share sheet or from your Mac.
- According to 9to5Mac, “sending a photo to the contact via the Photos app can allow them to access the message history and delete the conversation.”
Obviously, if you have a mischievous friend or vengeful ex, this is not the exploit that you need running around the world. Fortunately for everyone involved, when Apple (after some time) acknowledges the issue, a repair should be coming fairly quickly. As of this writing, though, it has not. Although, tomorrow is another day.