A new iMessage bug is causing issues when texting Android users
For some iPhone owners out there, a strange bug is potentially wreaking havoc on folks trying to text Android users.
![Messages icon](https://photos5.appleinsider.com/gallery/54493-110046-Messages-xl.jpg)
Messages icon
There are some iPhone users taking to social media to confirm that their device is running into a particularly strange bug. When they are trying to text an Android user, the iPhone is adding a "+" symbol to the beginning of phone numbers.
The problem isn't just related to texting Android users, but also people using Google Voice numbers. The bug appears to be only impacting iPhone owners in the United States.
Adding the "+" character forces the iPhone to recognize the number as an international one, even when it isn't. A normal U.S.-based number is automatically switched to an overseas one, causing delivery issues on both ends.
There are several threads on Reddit right now, with many iPhone owners pointing out their devices are running into the same issues. As of right now, there does not appear to be a reason for the bug.
It appears the bug is tied to the iPhone, with no specific callouts to people sending texts from the Mac. But with Macs relying on text message forwarding, it would seem reasonable that the issue would impact these users, too.
Apple's update to iOS 16.5 earlier today does not seem to be the root issue, as many iPhone owners are pointing out the issue cropped up for them before the updates were released.
As far as fixes are concerned, some users have suggested that sending a text to yourself may patch the issue. Some users have suggested the fix is already present server-side, while others say to simply change the formatting of the number to add "+1" to the front.
Read on AppleInsider
![Messages icon](https://photos5.appleinsider.com/gallery/54493-110046-Messages-xl.jpg)
Messages icon
There are some iPhone users taking to social media to confirm that their device is running into a particularly strange bug. When they are trying to text an Android user, the iPhone is adding a "+" symbol to the beginning of phone numbers.
The problem isn't just related to texting Android users, but also people using Google Voice numbers. The bug appears to be only impacting iPhone owners in the United States.
Adding the "+" character forces the iPhone to recognize the number as an international one, even when it isn't. A normal U.S.-based number is automatically switched to an overseas one, causing delivery issues on both ends.
There are several threads on Reddit right now, with many iPhone owners pointing out their devices are running into the same issues. As of right now, there does not appear to be a reason for the bug.
It appears the bug is tied to the iPhone, with no specific callouts to people sending texts from the Mac. But with Macs relying on text message forwarding, it would seem reasonable that the issue would impact these users, too.
Apple's update to iOS 16.5 earlier today does not seem to be the root issue, as many iPhone owners are pointing out the issue cropped up for them before the updates were released.
As far as fixes are concerned, some users have suggested that sending a text to yourself may patch the issue. Some users have suggested the fix is already present server-side, while others say to simply change the formatting of the number to add "+1" to the front.
Read on AppleInsider
Comments
Also, stop pretending there is actually an RCS standard that guarantees end-to-end encryption. We all know this isn't true, and that even the google implementation of "secure" RCS messaging is a CF.
Lastly, the blue/green hubbubble, is just a lot of nonsense over nothing. If Apple were to ever implement RCS, they'd add pink bubbles to indicate that another second rate protocol is being used so that users know that even though it isn't SMS, it's still not secure like a blue bubble.
Anyway, RCS can be made secure by Apple, and has been made secure by Google. Don't tell me Apple is less technically adept than Google. They absolutely can.
SMS will always and forever be a privacy and security hole that the carriers/others can exploit, and there's no user-friendly reason to cling to it. Ignores the other obvious advantages of RCS over SMS, ie media sharing, text reactions, etc. if you wish. What would be your argument against making the entire messaging system more secure? Because Apple doesn't want to? OK, that's a reason. Anything else?
I don't expect an answer, much less a debate, this thread isn't the right place for it; just food for thought.
This might explain why I didn't get any response to text messages I sent to a customer Friday. Yet another reason for me to remember calls are better than text for essential communication.
1. How little faith in Apple you have, or
2. How unwilling you are to admit a secure RCS in iOS would be good for Apple users.
Which is it? .
And, frankly, we all know that Google will abandon RCS in under 5 years when it fails because they aren't willing to actually put any real effort into making it something worthwhile but only invest in PR. I mean, really, how many times have we seen this story from them.
So I use Whatsapp?
Apple's messaging service can only be truly private when communicating with other Apple users until Apple creates a secure RCS in iMessage to go along with the secure RCS from the Google side. Apple is perfectly capable of doing so. Problem: Their profits are better if they don't.