Agreed 100%. All the problems lie with apple proprietary systems which are closed off to the rest.
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.
Apple Being Sued Over Phone-Switching iMessage Issue
- Thread starter MacRumors
- Start date
- Sort by reaction score
Agreed 100%. All the problems lie with apple proprietary systems which are closed off to the rest.
That would be ridiculous. Maybe Apple should help customers migrate from iOS to Android or Windows then?
Yes the fix I posted about a page earlier but nobody reads, they just post up freaking out... It's not magic, it's called reading.
If you expect most people to hunt around a long thread to find what you refer to, that's not too likely. The least you can do is quote your own post if you later mention a fix that you mentioned before.Yes the fix I posted about a page earlier but nobody reads, they just post up freaking out... It's not magic, it's called reading.
The said, just like many other suggested "fixes" it's not actually something that always works for quite a lot of people. There is still a problem on Apple's side somewhere that they themselves seem to acknowledge.
For those of you who didn't see it when I posted it on page 4 (I'm looking at you C DM), this is the "magical" fix that I allegedly didn't mention...
Not complicated except that reading about the issue and the thread would show that by far that doesn't do the trick for a lot of people. That's one the main parts of the underlying problem on Apple's side when it comes to all of this.
----------
Yes, I actually found it once you actually mentioned you posted it before. And I commented on it as well explaining that that's part of the problem that all these solutions are things that sometimes work for some people but a lot of times don't work for many others.
I read through page 6 and didn't see ONE person mention doing what I suggested... The problem is the phone number association to iMessage which is why if you go and delete the phone number that's having the issue from your Apple ID and just for good measure "unregister" the defunct Apple device that was being used for iMessage and give the servers a little time to update, it resolves the issue. I myself had to do some hunting for this solution some months back and a little of it was trial and error but it does work. It would be nice if it just automatically updated when you no longer have the device but alas it doesn't.
Yep exactly. Would also be great for traveling with no access to data.
They probably are stalling for obvious reasons, but I can understand people's dismay at someone suing over this. iMessage is an apple to apple service that sits on top of SMS. Nothing is stopping the SMS from getting through if the sender sent as such, just apples service has nobody to deliver to (unless recipient has other registered device). If they are being petty and not fixing it deliberately then I can understand people being angry, and it's bad business, but suing just reflects sone kind of sense of entitlement that many feel uncomfortable with.
I agree. I use and really like Apple gear. This is just a bug, but if not attended to in a timely manner, they are open to legal action. On one hand they could have just been slack, or it's a who cares for ex customers, hard to know
There have been other threads where people have tried all kinds of solutions including that one where it didn't work for them. Even Apple themselves mentions that things of that nature don't work for this and don't mention it as far as what should work.
I know you believe you have some secret useful total solution to this, and it likely has worked for various people and will work for some others (just as various other mentioned solitons), but unfortunately there's more to it in Apple's side where they have to make it all work correctly and consistently for everyone.
I'm not claiming to have some secret, I found this information online. It took a lot of searching and trying various "solutions" that I found before I found this one that in practical application worked consistently (for me at least). If this doesn't work for others, I'm sorry. I have actually used this fix several times. Maybe I am just lucky and this has worked for me every time I've used it. Not saying this "issue" isn't a pain in the butt. Not saying that this information that I provided is easy to find. I'm simply trying to supply a "fix" that I have consistently used. If I can make it easier for someone to find this information so that they can resolve their issue, then mission accomplished and that's all I'm after. If you disagree, that's your prerogative, doesn't mean I'm wrong or you're right. Maybe this is inconsistent in the grand scheme of things but I'm just trying to help. At least I'm trying to do something besides b!tching and suing...
And I said that this likely has helped some and will help some. But it doesn't seem to work for everyone (you can even see a reply from a poster just above already showing that it didn't work in his/her case). Meaning that it's something that can be helpful but not an actual solution as in one that actually fully takes care of it all for everyone at any/all the time. That's what I was trying to point out given that the way your posts were coming off is that there's really no issue here because there's a full solution to it all for everyone. Unfortunately it doesn't appear to be, and even Apple themselves (who would know better) doesn't even list it as a solution and even still admits they are working on the issue and this don't have a full solution to it yet. Again, not trying to out any of not down, just explaining that there is still and issue nonetheless and one that Apple still needs to fix.
That said, while potential workarounds that have some success are of course useful, given what's been going on so far with this and for how long it has been going on it seems like perhaps using might possibly be one way to go at this point to hopefully provide enough of a push for Apple to take it all at least a bit more seriously and hopefully put some serious work on it and perhaps finally resolve it properly for anyone/everyone once and for all.
I have a friend who recently switched to a Note 3. We've tried everything on the Apple forums, everything here, and read up and tried things on numerous other sites to resolve the problem. Nothing has worked.
After activating iMessage, it effectively hijacks the standard SMS/MMS protocols. They should be 100% responsible for fixing it or turning it off. There should be a better kill switch for disconnecting it, there are too many instances where it could be left on while swapping cell hardware: uneducated customers not knowing better, phone screen was cracked, etc.
After activating iMessage, it effectively hijacks the standard SMS/MMS protocols. They should be 100% responsible for fixing it or turning it off. There should be a better kill switch for disconnecting it, there are too many instances where it could be left on while swapping cell hardware: uneducated customers not knowing better, phone screen was cracked, etc.
Fair enough. I guess I didn't realize I was coming off as it being a be all/end all solution. I just think there are various convoluted ways to resolve this issue out there and suing is stupid and not the answer. The one thing I did experience with my "fix" is that it would take sometimes a day before this would make a difference as a lot of servers don't update immediately but might need to be recycled and/or only update certain services once daily before changes will take effect. I have worked in a NOC and have been responsible for this so I'm not just talking out of my butt.
Really? I'm going to sue you for not fixing a bug on your free service, in your free software quickly enough because I believe you did it in purpose and my feelings got hurt when I didn't receive enough birthday messages after swapping to android?
If apple didnt fix it deliberately, it's bad and I'm in no way defending them. But suing them? That's silly.
it's sad that it has to go to a lawsuit. But the threat of paying out a lot of money appears to be the only way to motivate Apple to fix an issue they have known about for year.
And the only people who are going to get paid out of this are the attorneys who file the class action suit. But I don't understand why anger is directed toward the people filing the suit vs. Apple for letting this problem fester for years.
----------
You are defending them. And minimizing the issue. But I bet if you didn't get your texts for week, you'd go apeschit. But it's easy to dismiss it when you're not the person impacted.
Free service with free software that all only works on paid (and fairly expensive) devices. Always fun to overlook that part of it all.
I disagree, it's a free and cool service but it's impacting message delivery, that's not good