iPhone 4s Message Failure

I'm having the same problem with my iPhone 4. I have ios 5 installed. My friends are telling me they're getting my messages from yesterday and sent repeated times. Any help would be nice.

I am getting the exact same thing. When I send the message, the bar at the top that tells you whether it's sent or not, never fully sends and then I turn off my phone and restart it and when I go back to the message it just says 'Message Send Failure'. But then I ask my friends whether they got the message or not and they keep saying they ARE getting the message but a day later and several times and I can't see their reply or call anyone. If you did get help with this problem, please let me know. Thank you.

Happens to me too. Yesterday, just now and a few days ago. Fixed it just now by going to airplane mode and back but I know it will happen again... No idea why it's happening. Both me and my friend have good reception!

I have an iPhone 4. This happens daily to me.

I have gotten sick of it and turned imessage off until I hear it's been permanently sorted out by apple.

It is a pitty because my son wants to get an iPod touch so he can message me when I'm away at work.

Hopefully it wont take to long.

I have the exact same problem. Sometimes the iMessage texts will go through in a split second. But 1/3 of the time it will get stuck sending, will fail, send duplicates, or not send the message at all (even though it said the message was delivered). Very very flakey. And it seems related to peak usage times. The day before and after Xmas I was hardly able to text at all. Most messages would fail, or would only send after 2-3 retries.

I just fixed my iPhone from saying that took for ever but try and turn on data roaming in the settings and try to send it again

Re: iPhone 4s Message Failure

Jan 6, 2012 7:04 PM (in response to Lotla)

I just fixed my iPhone from saying that took for ever but try and turn on data roaming in the settings and try to send it again

Like (0) Reply

I have Verizon. Was having the same issue and just did a roaming update by calling *228 and pressing #2 and it fixed the problem.