Q: iOS 7 iMessage won't activate

this worked for me! thanks so much for the tip.

went through all the fuss of reseting and restarting, backing up and restoring. geesh.

Apple just ran through all the steps that you read everywhere else on how to fix it. 

Also they wouldn't comment when I asked if there were heaps of people calling with this issue, or is there is high load on their infrastructure.

Basically the couldnt do anything and got me off the phone by saying that i should offically wait 24 hours without turning it on and off before i say its broken. (that is written on one of the help docs somewhere)

The problem is that i had it on for about 18 hours before i got the first error message and then it was on for about another 10 hours since, but not a continous 24 hours..  lol  so ill play their silly game...

The apple guy sounded frustrated as **** with the whole thing..  which gave me my answer to how many people were calling up with this issue..

thanks for the reply! i was just wondering. Is anyone else getting the same errors i am?

I'm having the same problem and like many people I've seen on here - NOTHING works for me.  I've already done everything - restore, wipe, backup restore, time and date settings etc and NOTHING works.  My iMessage is still not activating and is perpetually on waiting for activation. 

I am in the Philippines with GLOBE and while some people's upgrade with the same provider went without a hitch there also some of us who is experiencing this anomaly!

GAH! I am so frustrated!  This has happened to me once before and I hate that it's happening again.  Come on Apple - you have to do better than this.  Maybe next time roll out the updates for different regions at different times so that your servers don't get bogged down. 

SO UPSET and FRUSTRATED right now.

Yeah I have had the same errors as you. 

I get the "could not sign in, please check network connection" one when i am logging in and out with apple ID,

and i got "an error occurred during activation" after the first 18 hours attempt..

So its a very similar if not the same issue..

I'm on Telstra'a 24x7 chat trying to get someone to escalate it, but the level 1 technicians try to step through all the nooby troubleshooting copy and pasted instructions....... zZzz I've told them I've tried all that and then they ask simple things like "does your phone have an active Internet connection?"

I've seen some errors on the iPhone's console messages. Still can't see clearly why the iMessage registration isn't working:

ep 20 12:32:21 pong identityservicesd[54] <Warning>: [Warning] Registration failed for Registration info (0x14661510): [Registered: NO] [Type: Phone Number] [Device Name: (null)] [Service Type: iMessage] [Env: (null)] [Main ID: (null)] [Phone Number: (null)] [AppleID: (null)] [UserID: (null)] [C2K: NO] [Push Token: <da9e3b01 eb548f23 61034bc7 f6eb902b 9e6c125e e122f821 cf43ceb5 58436dbb>] [Region ID: (null)] [Base Number: (null)] [URIs: (null)] [Candidates: (

    "+6143xxxxxxxx"

Sep 20 12:32:22 pong securityd[87] <Error>:  SecErrorGetOSStatus unknown error domain: com.apple.security.sos.error for error: The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)

Sep 20 12:32:22 pong securityd[87] <Error>:  securityd_xpc_dictionary_handler sbd[110] DeviceInCircle The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)

Sep 20 12:32:22 pong Preferences[156] <Error>: mms: ***** isMmsConfigured = 1

Sep 20 12:32:24 pong Preferences[156] <Error>: mms: ***** isMmsConfigured = 1

Sep 20 12:32:24 pong Preferences[156] <Error>: mms: ***** isMmsConfigured = 1

Sep 20 12:32:24 pong Preferences[156] <Error>: mms: ***** isMmsConfigured = 1

Sep 20 12:32:24 pong Preferences[156] <Error>: mms: ***** isMmsConfigured = 1

Sep 20 12:32:24 pong Preferences[156] <Error>: mms: ***** isMmsConfigured = 1

Sep 20 13:04:16 pong CommCenter[68] <Notice>: Carrier bundle value for recipient address: +61418707634

Sep 20 13:04:16 pong CommCenter[68] <Notice>: queuing sms message with id 1073741833

I believe that phone number at the end is a local Australian number Telstra sends our iMessage activation SMS to but it's either not responding or not getting there..

I just had the same problem.  I kept trying etc.  it seemed to work when I turned the phone off and then on again.

I did this and it totally worked!

The same thing happened to me. I kept trying to log on to iMessage and Facetime for the last 24 hours and nothing worked.

I backed-up my iPhone 5 and then restored to the factory settings. After a clean install the option came up and asked if I wanted to rset up as a "new phone" or use "my backup". I chose backup and iMessage and Facetime works.

not only was the sales representative on the phone a new level of no help at all, as soon as i called them out for all resolutions costing me even more money just to get my imessage to work, magically my icloud wouldnt even update (but if i spend and extra $50.....it should work,,,,) this is ridiculous.

i tried it aand its gone....didnt work =[ again

Ditto for iMessage Activation problem with Telstra IP5s.

Virgin activated no problems.

Does sound like a Telstra-Apple issue.

I am with Telstra and my facetime AND iMessage won't acivate.  Tried rebooting, signing in and out of Apple ID etc...to no avail....haven't tried restoring yet...will wait a couple of days to see if it fixes itself (may be problem with Apple servers and/or Telstra being overloaded with activations...

backup -> restore to factory condition -> restore backup did work, but what a headache.  I also have to reload a lot of files.

I got into the Apple ecosphere precisely to avoid this nonsense.  It is supposed to just work.

Since Apple controls everything, the system is very rigid.  If anything happens, there is nothing else one can do but restore. 

Lohengrin9 wrote:

 

backup -> restore to factory condition -> restore backup did work, but what a headache.  I also have to reload a lot of files.

Tried that - didn't work on a new phone.