Apple confirms it is working to fix iMessage problems

Apple has acknowledged it is aware of an issue with iMessage that arose after updating its devices to iOS 7.

Like many iOS updates before it, iOS 7 has suffered a few teething problems, with this latest bug meaning that some users are unable to send or receive iMessages. The instant messenger service should provide free texting between users of Apple devices, but Twitter and Apple’s message boards have erupted with complaints from disgruntled iOS users saying that whilst messages initially appear to have been sent, a red exclamation mark will later appear to signal that this isn't the case.

Frustrated customers have reported other problems too, such as a glitch where the blue message sending progress bar freezes and remains frozen until the phone is restarted.

Should turning the device on and off fail, other temporary fixes suggested by users include disabling iMessage all together, resetting the Network Settings, then turning the iMessage back on.

In a statement to the Wall Street Journal, Apple said that it is aware of the issue that “affects a fraction of a percent of our iMessage users, and we will have a fix available in an upcoming software update.” It continued: “In the meantime, we encourage any users having problems to reference our troubleshooting documents or contact AppleCare to help resolve their issue. We apologise for any inconvenience this causes impacted users.”

The latest version of iOS was released 18 September and garnered praise for its visual redesign and new features such as a control centre that functions like a dashboard for managing an iPhone or iPad.

However, the last couple of weeks have been filled with a flurry of complaints about everything from excessive battery drain, typed letters not appearing on the screen, and Siri requests being misunderstood by the voice-recognition service.

Apple released an iOS update fix last week to tackle security problems, and it seems clear that a new iOS 7.0 3 isn't too far off the horizon.

404

Sorry! Page not found.

The article you requested has either been moved or removed from the site.