iMessage stuck on verifying my phone number

Having same issue as this, iMessages worked perfectly from the time I got the phone (i4S) turned iMessages off (don't know why) but ever since it won't verify my phone number. My email verifies but phone conitnually says verifying and then eventually says "verification unsuccessful".

Have tried:

- turning iMessages on/off

- resetting network settings (multiple times with iMessages on and then off)

- checked my phone number in Settings -> Phone (it's correct)

- changed my own phone number in contacts to include +61 country code.

- set time automatically (already set on this, I was sceptical anyway)

- hard reset

Don't really want to restore the phone. Just annoying that it WAS working then stopped...

Any more news on this front???

Thanks to jayeecordero (third item on this thread). I have tried many fixes over the last three days on both my phone and my friends - we were both having the same problem.

This worked for me.

I cannot believe it was so easy after so many other things failed.

I followed all of the steps but it didn't work. It will only let me add a new email and won't let me remove the email that's in there for iMessage. I can't even click on my phone number in iMessage settings because it's gray and has a loading symbol next to it. I tried turning iMessage off and on, Facetime, and tried restarting the phone. Nothing's working.

Same issue:(

thanks for the reply but it doesnt help

thank you! this totally helped for both facetime and iMessage 😎 i've been having this issue since yesterday

i have the same issue, facetime works tho but imessage is stuck on verifying...

This was PERFECT! completely fixed the problem. thank you!

Tried all of the above and every other forum soloution including restoring the iphone and still no luck.

Anyone else still stuck??

Yup...I have the same issue....phone number wont verify within the imessage app. Doing a reset of the network settings didn't work for me.

I have reset it and it is still stuck in verifying.

About 8 hours ago my daughter went and decided to change her Apple ID password unnecessarily, which seemed to freak out iMessage. I've turned it off and on, signed out, reset network settings, rebooted the phone, replaced the SIM, and other things, and the phone number is stuck on Verifying.

My theory is that the iMessage servers have locked her out because the phone tried to log in with the old password too many times.

At http://support.apple.com/kb/TS2755, under If you still can't send or receive iMessages, it says this:

iPhone automatically registers your phone number for use with iMessage during activation. If you encounter issues activating or using iMessage with your phone number:

• Verify that you are connected to a cellular network.
• Toggle iMessage off and on in Settings > Messages.
• If you are unable to activate iMessage on a device after remote wiping it, wait at least 24 hours and try again.

So I'm going to take a hint from that third bullet (even though this isn't a remote wipe situation), and just leave iMessage off for many hours to see if Apple's servers decide to play nice tomorrow.

I am still stuck 😟. I completely reset the phone. I tried the turning off and turning on thing too. Nothing worked. I can use imessage with my apple ID (facetime too) but My old number is stuck in there and it keeps saying "verifying". Also, when I put both facetime and imessage on it says "waiting for activation" and NOTHING happens...I'm starting to regret the switch to apple...blackberry was waaaay easier...

I'll appreciate any help I can get on this.

I have the same issue, nothing is working. I have tried all the steps above.... I have tried:

- resetting the network

- restoring the phone

- checking numbers

- making a new icloud account to see for changes

I have tried absolutely everything, does anyone have any options for us to try? Please I beg you HELP ME!!!

I was having this problem for a few day a while back. I didn't resort to a restore but tried all the other suggestions. The only thing that fixed it for me was to "quit" the settings app (and it would be a good idea to quit all open apps at this point). This fixed it immediately for me.