IMessage Fail

This past Friday, we went to Verizon to upgrade the my wife’s phone. She had been fighting with my old crappy Droid Bionic for the past year, so we made the trip THE day that the line was eligible for an upgrade. Since we moved from Las Vegas two years ago, we figured now was as good a time as any to change her phone number as well and ditch the 702 area code. The trip to the store lasted about an hour and a half and we left with a new number and a shiny white Galaxy S4.

Over the weekend, my wife asked me if I could figure out why she wasn’t getting text messages from her parents that they swore they were sending in response to her text stating she had a new number. Admittedly, I initially assumed that they were just doing something wrong and texting the old number (or some other number that wasn’t the new one); so, I blew it off at first. However, when I started getting group text messages from her parents that my wife was actually receiving, it struck my curiosity. How could it be that she was receiving their group messages but not their individual message?

As the weekend progressed, we noticed that the issue wasn’t just limited to her parents and that there were a few other members of our family — 3 to be exact — whose messages she also wasn’t receiving. It became obvious that the primary thing each person had in common was that they had various versions of the iPhone. There wasn’t a single person whose text messages that she was able to receive that had an iphone (that we knew of anyway).

After some digging, I stumbled upon this post that describes a known issue when you switch from an iPhone to Android. Essentially, you must log into your Apple account and de-register the old iPhone from your Apple profile in order to prevent other iPhones from attempting to send messages to your new (Android) device via iMessage. The only problem is, my wife NEVER had an iPhone.

I personally checked the messages on the phones of a few of those family members and verified that the messages that were being sent were showing up as iMessages, not texts. Also, none of their devices had the setting checked to only send iMessages and not send text messages (not that I really had to check this, because the messages worked fine in the morning and stopped in the afternoon — almost immediately after switching numbers).

While I cannot say with 100% certainty that my theory is correct; it appears that this was the problem my wife was experiencing. But, what I believe is that it wasn’t her who had not de-registered an iPhone — it was the person who previously owned her new number. I spoke with one of the networking engineers from Verizon this afternoon who said that it made complete sense (of course it does), but that there isn’t anything they can do about it. Since the number was put back into the pool — there’s no way to know who had that number before her. Furthermore, Apple is the one associating the number with an iPhone, so what could Verizon do?

So, we switched to a new number (again) and after factory resetting the device and reactivating it, the problem went away. All of those people who have iPhones can now text her without issue.

So, what’s wrong with this picture? If you have an iPhone and you message someone, your message obviously gets sent through the iOS gateway first in order to determine if the person on the other end has an i device. If the Apple infrastructure recognizes that number, it routes the message via iMessage rather than dumping it off as an SMS through the carrier. But, what happens when someone who had an iPhone drops their number and it goes back into the pool. What are the chances that they know or care enough to go to Apples website to de-register their device so the person that gets the number can receive texts from iPhones. Not very likely. Perhaps after some allotted amount of time the Apple infrastructure picks up that this number isn’t valid and corrects itself, but I’m not betting on it.

iMessage has only been out since 2011 — so, it’s possible that this is a ticking time bomb. Then again, the average person would have just assumed that the Verizon’s network sucked and that was why the texts weren’t being delivered.

Comments