Tuesday 1 October 2013

Problems with iMessage in iOS 7.0.2 and how to solve it temporarily

Lately, iOS 7 times usually more news for its failures than for its innovations. In the first problems that gave the possibility to access the locked terminal, and supposedly, cured with iOS 7.0.2, now added another incident ofiMessage malfunctions.

You can read the Apple support forums numerous complaints from users that indicate the existence of problems in theiMessage service with the latest update of iOS 7.
For those who do not know is this, iMessage becomes the Apple WhatsApp, ie an integrated messaging service withiPhone SMS Manager which, when it detects that the receiver is another iOS device or a Mac, use internet instead of sending a standard text message.

Multiple errors in messages

The problem has now come with the upgrade to iOS 7.0.2, which came to solve the problem of unauthorized access to the locked, and now has problems with iMessage.
A significant number of iPhone users have indicated they see as their messages are not sent, not received by the recipient or, instead of being sent over the internet, ie free, sent as SMS, with the cost that this entails according to their rate.

A problem from the beginning of iOS 7 worsens in iOS 7.0.2

Get listed in AppleInsider , this problem seems to come long since the first complaints came on the same September 18, iOS launch day in July, and it looks like are increasing, especially since the arrival of iOS 7.0.2 the week last.
At least, in the same forums found a temporary fix until Apple solves this problem in the next update of the operating system:
- Disable iMessage in Settings> Messages.
- Reset network settings in Settings> General and reactive iMessage.
This method seems proven, even in another reference sites information from Apple, MacRumors, assert their validity.There are also variations thereof include turning off the terminal for several minutes.
Has anyone noticed these problems? Did you solved with the proposed method? Leave us your thoughts in the comments.

No comments:

Post a Comment