Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Curious iPhone Bug Causing Non-iMessage Texts to Display Extra + Character, Breaking Conversations
- Thread starter MacRumors
- Start date
- Sort by reaction score
Oh, I'm sure iOS 17 will solve everything...
While possible, the coincidental timing with a new release of iOS makes that seem less likely.
Was messaging a friend today. Me, iPhone. They, Android. Their messages had the extra character and their responses would land in a new chat and not in the chat where we were messaging. Weird.
Further, the chats from where I was messaging were to the number I had in my Contacts. Their replies came back from the same number but with no spaces between number - just a long string of numbers.
Further, the chats from where I was messaging were to the number I had in my Contacts. Their replies came back from the same number but with no spaces between number - just a long string of numbers.
Who texts android people? This is a non-issue.
/s
/s
IOS/iPadOS 16 has been a buggy mess since launch.
Seriously hoping they have things straightened out by the 17 rollout.
Hoping…
Issues like this (usually phone calls though) have been going on for years and affect iPhones and Android phones randomly.
Here’s a discussion: https://community.t-mobile.com/acco...incorreclty-showing-as-foreign-countries-9289
Mostly iPhones but there are some people with Samsungs or other phones who have problems like that.
I’m not saying the iOS update has nothing to do with this messages issue but similar problems have happened for years that affect both iOS and Android.
Using Verizon here so it is across all carriers. Mine quit working, again, this morning when texting my android friends. Basically nothing gets sent. Yes I have updated network settings, etc. It starts working again on its own so it is definitely on the carriers to figure out what is going on.
Issue I have is if I receive an MMS from an android user that is already in my contact list with +1 country code it creates a new thread when they send me picture messages to my iPhone.
This has happened to my iPhone 13 Pro Max numerous times in the past. I decode the number and see it's local but there is a "+" in front. Why is this a big deal today?
Meh. It's been horse crap since iOS 7. iOS 5 and 6 were the last ones worthy of the name iOS.
Yes.. #BringBackForstall
He was the only one other than Steve that cared more about it, since it was his baby after all. Airplay has been horrible since then, too. Back in iOS 5, I could airplay a video, and put the device to sleep and it would keep going as it should. Now... it's an undefined event... and the whole thing explodes.
Airplay 2 is a mess that no one wants to admit. The new fluid interface is horrrrrrrible. One of the worst UX designs imaginable. The keyboard is one of the worst since they moved the key spacing and touch targets. The teeny tiny scrubber dial in videos and music is epic stupid. Combine with the stupid fluid interface layer, it's nearly 100% inaccessible. Dumb UI and UX choices everywhere.
Craig is great, but he's no Scott or Steve with the eye and obsessive on for detail. Tim couldn't care less, and Jeff doesn't even know what to do with it apparently. Sigh.
Mediocrity is the new way for software at Apple. Just like the good ol' Gil Amelio days....good times.
I disagree only slightly. 12 was near perfect, for the phones that were released with it. 8 and 11 were horrible. 11 was where Apple pulled all their dirty tricks to kill older devices, which they pulled back on when states started mass suing them.
Because we live and travel internationally we have all our us contacts with a +1 before their phone numbers.
My sister for years has had problems with her incoming and outgoing messages ending up in separate non integrated threads. If there are multiple parties in the threads it results in multiple threads.
But the problem isn’t consistent. And it doesn’t seem to be caused by recipients being non iMessage users.
Funny this article came up because I submitted a feedback today on her problem.
Hopefully their + fix for everybody else fixes her chronic text issue.
My sister for years has had problems with her incoming and outgoing messages ending up in separate non integrated threads. If there are multiple parties in the threads it results in multiple threads.
But the problem isn’t consistent. And it doesn’t seem to be caused by recipients being non iMessage users.
Funny this article came up because I submitted a feedback today on her problem.
Hopefully their + fix for everybody else fixes her chronic text issue.
US or more accurately, NA, is a bit of an outlier on international long distance dialing
Whereas other countries outside CC 1 dial 0049 (landline and mobile) or +49 (mobile only), US uses 01149 (landline and mobile) or +49 (mobile).
Too bad there’s not a global standard around just the + and 00.
Lol, complain of bugs in 16 but eagerly await 17 BETA full of bugs. 🤣
More likely a carrier issue caused by a change in iOS.
I mean there is a global standard. Just the +1 countries cook something else to be fair.