I was affected too. Turning off iMessage and back on seems to have fixed it but only after a day of messaging issues. Confidence in the service is lowered as a result. I also noticed that prior to turning off iMessage that the fall back to SMS was disabled which compounded the issue for me. This wasn't before so I'm assuming the IOS 7 update or 7.02 changed this setting on my iPhone 5.
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 Aware of iOS 7 iMessage Issue, Working on a Fix
- Thread starter MacRumors
- Start date
- Sort by reaction score
Seconding
Yes, same here. I'm currently deployed overseas and have my cell data turned off and am just using WiFi when available to avoid outrageous roaming charges. I thought initially that this was due to my cell phone number not being able to be pinged but after reading some forums online I discovered the reset method. Everything works fine now for me, for what it's worth.
What sucked too is I use my macbook pro more than my cell phone to send imessages back home and even that had gotten messed up because of the update. However, it was quickly fixed with the reset from the phone. I panicked because my girlfriend back home was saying "don't download iOS 7! It's not worth it!" I didn't want her to have a 1UP on me haha... I could hear her saying, "I told you so!!" Boy was she wrong, iOS 7 is great save for this small issue. I hope everyone else can get theirs fixed if it's not fixed yet!
Yes, same here. I'm currently deployed overseas and have my cell data turned off and am just using WiFi when available to avoid outrageous roaming charges. I thought initially that this was due to my cell phone number not being able to be pinged but after reading some forums online I discovered the reset method. Everything works fine now for me, for what it's worth.
What sucked too is I use my macbook pro more than my cell phone to send imessages back home and even that had gotten messed up because of the update. However, it was quickly fixed with the reset from the phone. I panicked because my girlfriend back home was saying "don't download iOS 7! It's not worth it!" I didn't want her to have a 1UP on me haha... I could hear her saying, "I told you so!!" Boy was she wrong, iOS 7 is great save for this small issue. I hope everyone else can get theirs fixed if it's not fixed yet!
you don't need to reset the Network Settings
I had this issue after every iOS7 update
resetting the Network Settings is kinda PIDA as you loose all WLAN settings
what worked fine for me was
1.) turn off iMessage
2.) reboot device
3.) turn on iMessage (and confirm the prompt)
after this i got the status info of undelivered iMessages (which i didnt before) and new iMessages were delivered successfully.
I had this issue after every iOS7 update
resetting the Network Settings is kinda PIDA as you loose all WLAN settings
what worked fine for me was
1.) turn off iMessage
2.) reboot device
3.) turn on iMessage (and confirm the prompt)
after this i got the status info of undelivered iMessages (which i didnt before) and new iMessages were delivered successfully.
Nice BUT how about someone pointing out the fact that iTunes 11.1 under MacOS 10.8.5 keeps crashing for a lot of people right now... to the point where I can't go 12 hours without it stopping... App Not Responding requiring a forced quit and restart. This only happened starting with the latest update. Look at the Apple discussion boards....
the title of the news should be:
Apple aware of releasing new expensive products with bugs, selling a lot first, fixing bugs later
Apple aware of releasing new expensive products with bugs, selling a lot first, fixing bugs later
How to fix iMessage
If what is posted above does not resolve and issue persists:
Follow instructions here: http://support.apple.com/kb/TS4268?viewlocale=en_US and if persists below should solve your iMessage issues.
1. Sign out and Turn off BOTH iMessage and Facetime (both use same device token)
2. Backup iTunes or iCloud (either one)
3. Settings -> General -> Reset -> Erase all Content and Settings
4. On the device complete iOS setup and Setup as New (skipping all the AppleID and iCloud parts to sign in)
5. Settings -> Messages and sign in iMessage
6. Send a "test message" to self using your own AppleID email address
7. Send a "test message" to self using your own phone number
8. If resolved restore from iCloud or iTunes backup
Facetime and iMessage use both a Server Token and Device token. Erasing device and restoring from backup resets the device token and resetting your appleID password resets the server token.
If having issues with iMessage and Sprint call them and ensure they have the correct ICCID provisioned that matches your iPhone. Also, if you have Sprint and integrated Google Voice then yes that may cause iMessage issues and you may only be able send iMessage using your AppleID, not with your phone number.
If what is posted above does not resolve and issue persists:
Follow instructions here: http://support.apple.com/kb/TS4268?viewlocale=en_US and if persists below should solve your iMessage issues.
1. Sign out and Turn off BOTH iMessage and Facetime (both use same device token)
2. Backup iTunes or iCloud (either one)
3. Settings -> General -> Reset -> Erase all Content and Settings
4. On the device complete iOS setup and Setup as New (skipping all the AppleID and iCloud parts to sign in)
5. Settings -> Messages and sign in iMessage
6. Send a "test message" to self using your own AppleID email address
7. Send a "test message" to self using your own phone number
8. If resolved restore from iCloud or iTunes backup
Facetime and iMessage use both a Server Token and Device token. Erasing device and restoring from backup resets the device token and resetting your appleID password resets the server token.
If having issues with iMessage and Sprint call them and ensure they have the correct ICCID provisioned that matches your iPhone. Also, if you have Sprint and integrated Google Voice then yes that may cause iMessage issues and you may only be able send iMessage using your AppleID, not with your phone number.
well, to be fair, a 'fraction', could be ANYTHING. A FRACTION could be 2/3's the people!!
Sorry, but this is wrong. They never said "a fraction of a percentage". Their exact words are a fraction of a percent". "A percent" is exactly 1%. A fraction is a portion of that, a portion smaller than the whole 1%, of course. If that's not what Apple means, or even if it's what Apple means and such is not the true number, those are other issues.
The fact is that they are being very clear (for those with a very basic knowledge of English and Math) that the problem affects less than 1% of iOS 7 devices. True or false, that's what they're saying.
Walt Mossberg and Kara Swisher are leaving the WSJ at the end of the year, so that might change. Of course, one of the rumors is that they are headed to the NY Times, so maybe not.
Nope, that's not being fair at all. it could be 2/3 of a percent, which would be 2/3 of 1%, which would be approximately 0.667%.
Mind you, I'm not saying that they are telling the truth. Just that they are claiming it to be a very small number.
Well after having this issue on Sunday evening and fixing it Monday morning, it has been working fine until about an hour ago. Just gone through the turn off/on iMessage and reset networking dance again. I hope this 'fix' from Apple comes soon.
2 out of 3 iPhones have this problem in our household. After wasting hours trying to fix it we had decided to just disable iMessage. We are both on metered data plans, so it makes no sense to waste data to send text's and pictures since our plans have unlimited text'ing/picture messaging. - Good bye iMessage.
I have been paying for unlimited text since my 3GS, so... the issues with iMessage are moot for me. I still have unlimited SMS...
What does that have to do with this problem? How is SMS helpful when messages are stuck? If it would fail back to SMS, people could probably live with it until there is a fix. But in this case it doesn't.