Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
That it took Apple so long is inexcusable. They should be really ashamed of this poor customer treatment.
 
I'm going to do this just because I've run out of data for the month, and I'm getting messages through my iPad but not my phone. I'll turn it back on in a few days.
 
Well thanks...I tried this and added my new mobile number, but it did not work. My iPhone still wants to send me my verification code to my old number. Still don't know why it is doing this, or if it is something programmed into the phone.

Do you have 2 step verification on? If not, turn it on and make sure you add you're new cell number too, that should fix your issues.
 
Now if they could fix the issue where some people want to turn off iMessages when they run out of data and can't get SMS from friends, that'd be great. Not a problem for me, but I've tried to help people on MR try to find a solution and couldn't.
 
This is several years over due. It is sad it took a law suit for apple to fix the basic flaw in their system making like hell if you wanted to leave iOS. It showed apple's shear arrogance that they thought no one would want to leave. This should of been done very early on and code wise is fairly easy to do unless your db designed is complete and utter crap.

One simple SQL statement is all it should of taken and then the code to fire up.

Delete from phonenumber where number =?.
Something like that. Nothing crazy as it should be in a separate table. Workaround is set said phone number to "" or null.
Glad to hear you're so much better at programming than Apple. What have you made?
 
This is several years over due. It is sad it took a law suit for apple to fix the basic flaw in their system making like hell if you wanted to leave iOS. It showed apple's shear arrogance that they thought no one would want to leave. This should of been done very early on and code wise is fairly easy to do unless your db designed is complete and utter crap.

One simple SQL statement is all it should of taken and then the code to fire up.

Delete from phonenumber where number =?.
Something like that. Nothing crazy as it should be in a separate table. Workaround is set said phone number to "" or null.

Geez, did you just take an "intro to programming" course? Because that is an extremely naive comment. Here: try to imagine how messaging works, and then try the figure out where this DB table would have to reside, who owns it, and how they would even know that a table record would legitimately have to be deleted, in a way that would not be susceptible to fraud.
 
Geez, did you just take an "intro to programming" course? Because that is an extremely naive comment. Here: try to imagine how messaging works, and then try the figure out where this DB table would have to reside, who owns it, and how they would even know that a table record would legitimately have to be deleted, in a way that would not be susceptible to fraud.
Well I tried to make overly simple but guess the blind defense of Apple is strong.
It should be relatively simplistic to do and sure of hell should not of taken 3 years.
If it was insanely hard to do someone screwed up in setting it up.
But hey apple can do no wrong. Oh Btw I do deal with stuff like this for a living.
 
Well I tried to make overly simple but guess the blind defense of Apple is strong.
It should be relatively simplistic to do and sure of hell should not of taken 3 years.
If it was insanely hard to do someone screwed up in setting it up.
But hey apple can do no wrong. Oh Btw I do deal with stuff like this for a living.

This was not the first resolution. People dealing with this obviously had a working cell phone (where else would they expect to be receiving SMS?), which means this issue has and had been resolved through calling AppleCare.

All this tool is is a faster solution than calling AppleCare. Please stop spreading misinformation that it "took 3 years."
 
way too late but better late than never.

better yet there should be no need for this. iMessage should be designed better.
 
This was not the first resolution. People dealing with this obviously had a working cell phone (where else would they expect to be receiving SMS?), which means this issue has and had been resolved through calling AppleCare.

All this tool is is a faster solution than calling AppleCare. Please stop spreading misinformation that it "took 3 years."
Simple fact is that calling apple should never of been required. This tool is 3 years overdue. Please stop defending apple on their massive screw up and arrogance. This should of been something easy to do not jumping threw a long list of hoops. You clearly never have been on the hoop jumping rout to undo iMessage. So no it is not miss information. This tool is 3 years over due.
 
This tool is not overdue, it is NOT even required!

Is people so dumb? How hard is it to disabling iMessage before transfering the sims. Common sense people.

:rolleyes:

"Is people so dumb?" - You seriously think you're qualified to report on the intelligence of others?

As someone who experienced this issue when I made the decision to switch to Android in March, I can tell you that it absolutely was not that simple. I switched off iMessage a week before I made the switch. I also removed my number from my Apple account in every place possible, and I still had MAJOR issues. I'm much more technically inclined than the average user and I took every possible measure to avoid a problem before I switched and it didn't help. In researching it, it was obvious that the problem has been going on for YEARS and Apple simply refused to fix it or even acknowledge that there was a problem. The information available on their website claimed that it was as simple as disabling iMessage and also that it might take up to 45 DAYS. Absolutely ridiculous.

Even two weeks after I made the switch, having taken all possible preparations in advance I was still having issues. I was even having issues with iPhone numbers that I had never once texted before I made the switch. I verified through testing that texts to my phone from an iPhone number I had never called or texted before did not go through. It only worked when I changed the default option for "Send as SMS" from off to on. Btw, upon the switch to iOS7 Apple reset that option to off for all iPhones regardless of how it was set before the update ensuring that this problem would continue, since surely an iPhone user is so concerned about using up their text messages that they would prefer for failed iMessages not to be sent as texts. They also don't want to be notified that their message failed to send.

It's pretty obvious why Apple refused to fix this problem until they were sued. It made people who switched away from iPhone think there was a problem with their new phone. They switched and all of a sudden they're not getting their text messages. 99% of users would think that the problem was with their new phone, and they did. Apple not only hurt their former customers with their actions, they also damaged the businesses of other manufacturers, retailers, and carriers. Hopefully those businesses are able to sue Apple for the damage they intentionally caused.

Apple fans - admit it, either Apple is totally incompetent or Apple was maliciously holding former iPhone owners numbers hostage to trick them into thinking there was a problem with their new phone. Take your pick. I'm willing to concede either, but I don't think they're stupid. They're very good a manipulating the uninformed.
 
Simple fact is that calling apple should never of been required. This tool is 3 years overdue. Please stop defending apple on their massive screw up and arrogance. This should of been something easy to do not jumping threw a long list of hoops. You clearly never have been on the hoop jumping rout to undo iMessage. So no it is not miss information. This tool is 3 years over due.

Lol, I have an GS5 and 5C and switch back and forth multiple times a week.
Number of times I needed to get help turning off iMessage: 0.
 
So this is why there are so many iPhone users who have not switched to Android. *sarcasm*
 
Lol, I have an GS5 and 5C and switch back and forth multiple times a week.
Number of times I needed to get help turning off iMessage: 0.
Then consider your self lucky. I been in the side where a number would not get released.
But hey blindly defend apple. There is not excuse for this take 3 years. You have to remember to turn it off on the phone and then hope it works.
 
This is several years over due. It is sad it took a law suit for apple to fix the basic flaw in their system making like hell if you wanted to leave iOS. It showed apple's shear arrogance that they thought no one would want to leave. This should of been done very early on and code wise is fairly easy to do unless your db designed is complete and utter crap.

One simple SQL statement is all it should of taken and then the code to fire up.

Delete from phonenumber where number =?.
Something like that. Nothing crazy as it should be in a separate table. Workaround is set said phone number to "" or null.

Should of? :confused:
 
Cool to see the tool land.

I think the sender may need to check his or her contact database. Make sure ex-iPhone users are not set to iPhone. ;-)
 
Then consider your self lucky. I been in the side where a number would not get released.
But hey blindly defend apple. There is not excuse for this take 3 years. You have to remember to turn it off on the phone and then hope it works.

Well, they have rolled out to hundreds of telcos in 3 years. Also becomes the most secure mainstream communication service in this timeframe.

Fixing this probably required a lot of testing too, given that they were rolling out major iOS releases every year.

It's the users' faults for not turning off their iMessage account before they switched. I think there was a bug in iOS7 that messed up the setting but it was fixed after a month. Craig Federighi mentioned it in an article I *think*
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.