Apple To Face Lawsuit For iMessage Glitch
An anonymous reader writes "We've all heard about iPhone users switching over to Android-powered phones and no longer being able to receive text messages from friends and family still using iPhones. Well, a woman with exactly this issue has filed a lawsuit against Apple, complaining that '[p]eople who replace their Apple devices with non-Apple wireless phones and tablets are "penalized and unable to obtain the full benefits of their wireless-service contracts."' To be specific, '[t]he suit is based on contractual interference and unfair competition laws.' She is seeking class action status and undetermined damages."
This is the kind of anti-competitive behavior that gets companies in trouble and causes regulatory crackdowns. Phone companies that make it hard to switch carriers. domain registrars that make it hard to switch registrars, and banks which make it hard to switch banks have all gotten in trouble for this.
Not an Apple hater, but I went through all of the correct steps to disconnect iMessage when switching to Android and had the exact same issues. Text messages wouldn't come through from iPhone users, at all, period. This is completely within Apple's control even if they aren't claiming it- the SMS protocol should always be used as a backup when iMessage transmission doesn't successfully complete. Otherwise, it's purely noncompetitive and is a maneuver to keep you on Apple's platform.
The people sending you messages are not sending you SMS, they are sending you iMessages. They are sending to your contact phone number, and they have iMessage turned on to save them $$$ when sending texts to other people registered with iMessage.
Because you used to have an iPhone, and had also turned iMessage on, your phone number is in their database, and so when it's deciding what data channel to use, it looks up the phone number it's about to send to, and if it's listed in the iMessage database, it sends an iMessage to the associated AppleID instead of sending an SMS via the cellular network. This way it doesn't cost them SMS $$$ to send the message.
When you pulled the SIM from your iPhone, you stupidly failed to turn off iMessage in your settings, and then sync those settings back to the iCloud. As this knowledge base article indicates, it can therefore take up to 45 days before it starts using SMS again: http://support.apple.com/kb/TS...
Alternately, you can go to http://appleid.apple.com/ and log in with your Apple ID, and manage your account, and disable iMessage that way (typically by removing your mobile phone number, and if you don't have an land line, putting the number in for your (non-mobile) contact number instead.
Note: Once the message has been sent, either via iMessage, or SMS, from the originating phone, it's sent; you don't get a second shit. It's not like those messages are "stored up" in a system that's capable of sending SMS messages, since the decision was made on the senders iPhone, not on the back end server.
Basically, it boils down to the former iPhone user being an idiot about disengaging from the additional iPhone associated services that they opt'ed into.
But never fear, up to 45 days afterward, the switch will happen automatically, as iMessage feeds back into the configuration database that the messages sent to the number have been undeliverable via iMessage. Or, you know, they could log onto http://appleid.apple.com/ now and fix it themselves, which can take up to 24 hours to take effect, because some idiot thought NoSQL was a good idea.
As an IT Architect, who daily works with and for those with varying degrees of technical skills, I would disagree that the user is "an idiot". The steps you mention will certainly address the issue no doubt. What is in question is if the layperson should be aware of these steps and be capable of undertaking them "if" they forget to disable iMessage. What a class action lawsuit will do is force Apple to put in checks that look at the IMEI of the phone each time an iMessage is sent and the ack isn't received by the server from the phone in x amount of time. There is a different error message for an IMEI either offline or registered to a new user than one where the phone is simply unavailable. I can think of 5 different ways Apple can identify the device changed to a non Apple device. They haven't fixed this issue on purpose. Creating an issue like this undoubtedly ensures a percentage of users return their Android phones and get another Apple device to fix the texting issue thereby ensuring Apple revenue. You can bet Apple will weigh the cost of the suit versus the customer retention revenue and either pay out and leave it the way it is or fix the problem. There's no doubt it is a problem because it's not automated and the courts will rule in favor of the user because the process is not automated.
This is a very real problem. My wife had her iphone 4s stolen and activated my daughter's old iphone 4s on her verizon line. About a week later she tells me that many of her friends are saying that she isn't responding to txt messages and she says she isn't getting them. This goes on for weeks. It turns out that she didn't turn on icloud on the new (old) iphone so all of the imessages were going to never never land. It's not obvious at all what is happening.
Zoid.com
But from the users POV the apple device and all its infrastructure is gone. They got a new phone. Why should they have to switch off stuff on the old phone?
http://michaelsmith.id.au
In other news, a friend of mine recently switched to Google Chat. Why hasn't he responded to all my Skype messages? Is he not getting them?
It turns out that she didn't turn on icloud on the new (old) iphone so all of the imessages were going to never never land. It's not obvious at all what is happening.
The first thing I would do after activating an iPhone on a plan to replace another one is sign into my iCloud account to sync all my contacts back. Not to mention remove the old iPhone from my iCloud account so my iCloud email, Safari bookmarks (and possibly saved passwords) are no longer in the thief's hands.
Apple doesn't make it hard. She just didn't follow instructions prior to selling her device and she hasn't followed instructions after selling her device to fix it. The hard part is pure fiction.
I find it constantly disappointing the repeated lie of "just works". The truth is this is only partially true even within Appleverse, there is no good reason why complicated workarounds are necessary. The fact that fruit lovers like yourself are prepared to defend, an anticompetitive move.
Personally I think this kind of bullshit is driving customers (like the one in the lawsuit) to android. You can only be abusive while your on top, and Apple peaked last year with market share; its devices are behind the competitors...they are the little overpriced phones, and they need to buy a headphone company to remain cool.
Right now, it is this but 45 days.
When I travel, I generally take a burner phone with me so I don't get overseas charges and otherwise. I still take my iPhone, but leave it on Wifi only. And a lot of times, Wifi is still hard to come by. I can get to internet cafes where I can log in to someone else's computer, but I can't get to my own computers. And when I do get wifi? I get all my messages, sometimes a week later.
The point? For a lot of us 1 day is way too short. Maybe 45 days is too long. What is the appropriate time?
A user preference would be appropriate.