Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
That's true, but if they keep the release cycle of one year and are already three months ahead of releasing the first developer beta of 10.12 (or whatever), they have to work on the next major version at the same time.

It was not El Capitan's fault by the way. A clean install of 10.8.5 can't login to iMessage too.

Going to Yosemite now 1Password 4 is too unconfortable, I need some of the newer features.

Edit: I had to create an app-specific password for iMessage and Facetime on Yosemite and it's working now.

All a server issue from what I read last.

Upgraded 2 MBPs a day later and did not run into any problems.
 
I experienced this issue myself and fixed it two days ago by removing all iMessage entries under "sessions" in Keychain. This led me to believe that this is not so much a server issue but more likely a certification issue. Apple's efforts to improve the security of their operating systems and online stores have caused most of their recent debacles. People will remember discoveryd in Yosemite and expired certificates with the App Store. The problem is not so much with Apple's software team in general but with their security team within (iTunes is a different story altogether).

Long story short, clean install causes users to unable to sign in FaceTime and Messages but not simple upgrade probably because there is a safety mechanism in place to require the key signer for these two programs to match the actual machine that is using these two programs.

It's the same way that clean install will produce a phantom set of bookmarks from your previous Mac OS X or iOS in Safari. Apple has no way of "unregistering" or "retiring" certificates and signed keys on iCloud. They probably just recently increase the security requirement so now simply having the right username and password isn't enough to get iCloud to work. The keys won't work if the original signer is different from the machine.

What's interesting is that simply deleting the current keys forces the iCloud server to regenerate a new set of keys. I hope Apple isn't planning on tightening the noose even more in the future by forcing users to not be able to do clean installs unless a master signing key is kept (much like how some financial institutions require clients to do for online transactions).
 
Last edited:
A year later and I'm facing the same problem. Although I don't have iMessages (Lion OS X) I'm unable to log into FaceTime. The error scheme is the following:

  1. FaceTime is launched.
  2. AppleID and the password are entered.
  3. Success on logging in.
  4. "Enter your e-mail address which you will use calling other people" (don't guarantee the exact wording)
  5. Entering the second e-mail (in fact optional for the testing purpose since entering it changes nothing)
  6. Displays "Verified" stamp with subsequent rejection. Alert text in red "Server was unable to verify your registration data" (not the exact wording as well)
After reading some messages in this thread I remembered that I was doing re-install (not a "clean" one) of Lion a month ago. I did suspect this had to do smth with Keychain but failed to figure exactly what. I deleted some entries under "Login" section bearing "me.com" (there're lots of those still left), restarted, of course, no result. What gives?
 
Last edited:
I gave up a while ago. I'm guessing the only solution for me is a clean install of OS X, problem is that I have a non-EFI graphics card so I'll have to wait until I acquire a legit Mac card for that. Oh well.
 
I experienced this issue myself and fixed it two days ago by removing all entries under "sessions" in Keychain. This led me to believe that this is not so much a server issue but more likely a certification issue. Apple's efforts to improve the security of their operating systems and online stores have caused most of their recent debacles. People will remember discoveryd in Yosemite and expired certificates with the App Store. The problem is not so much with Apple's software team in general but with their security team within (iTunes is a different story altogether).

Long story short, clean install causes users to unable to sign in FaceTime and Messages but not simple upgrade probably because there is a safety mechanism in place to require the key signer for these two programs to match the actual machine that is using these two programs.

It's the same way that clean install will produce a phantom set of bookmarks from your previous Mac OS X or iOS in Safari. Apple has no way of "unregistering" or "retiring" certificates and signed keys on iCloud plus they probably just recently increase the security requirement so now simply having the right username and password isn't enough to get iCloud to work. The keys won't work if the original signer is different from the machine.

What's interesting is that simply deleting the current keys forces the iCloud server to regenerate a new set of keys. I hope Apple isn't planning on tightening the noose even more in the future by forcing users to not be able to do clean installs unless a master signing key is kept (much like how some financial institutions require clients to do for online transactions).
[doublepost=1489863737][/doublepost]Hi. In keychain access i did not find a heading "sessions". Can you please explain? THANKS. It's been a year since I could sign into iMessage!
DG
 
[doublepost=1489863737][/doublepost]Hi. In keychain access i did not find a heading "sessions". Can you please explain? THANKS. It's been a year since I could sign into iMessage!
DG

The language of my system is French so the terminology is probably different. It's the first item on the left, of the top panel. It's just above iCloud (your system configuration could vary) and has a keylock sign. It's called "login" in English I believe.

When I say "all entries", I meant all entries related to iMessage (iMessage Signing Key and iMessage Encryption Key). You should not remove other items. Do this at your own risk.
 
Last edited:
A year later and I'm facing the same problem. Although I don't have iMessages (Lion OS X) but I'm unable to log into FaceTime. The error scheme is following:

  1. FaceTime is launched.
  2. AppleID and the password are entered.
  3. Success on logging in.
  4. "Enter your e-mail address which you will use calling other people" (don't guarantee exact wording)
  5. Entering the second e-mail (in fact optional for testing purpose as entering it changes nothing)
  6. Displays "Verified" stamp with subsequent rejection. Alert text in red "Server was unable to verify your registration data" (not exact wording too)
After reading some messages in this thread I remembered that I was doing re-install (not "clean" one) of Lion a month ago. I did suspect this had to do smth with Keychain but failed to figure exactly what. I deleted some entries under "Login" section generally bearing "me.com" (there're lots of those still left), restarted of course, no result. What gives?

Probably should delete all items related to iMessage (iMessage Signing Key and iMessage Encryption Key) or its equivalence in Lion. FaceTime on all macOS versions uses the same certification system.
 



MacRumors has been receiving a growing number of complaints from customers who are unable to log into iMessage and FaceTime after updating to OS X 10.11.4, which was released to the public on Monday. There are threads covering the issue on the MacRumors forums and the Apple Support Communities, along with user complaints on various social media networks.

The majority of the complaints are coming from users who did a fresh install of OS X, requiring them to log into the FaceTime and iMessage services. When attempting to sign in, an error pops up or nothing happens after entering an Apple ID and password, as seen in the video below. Customers who have recently purchased a new Mac also appear to be affected, and while most customers with login problems seem to be running OS X 10.11.4, there are also reports from those using earlier versions of OS X.

Apple support has been advising users to try logging out of iCloud and disabling two-factor authentication, but these fixes have not worked for most users. Apple's system status page is not listing any outages, but it appears there may be a problem with the iMessage and FaceTime activation servers. One customer who purchased a new Mac was told that Apple's engineering team is aware of the issue and is working on a fix.

messagesactivationerror-800x493.jpg
Affected customers have been unable to log in since first upgrading to OS X 10.11.4, and so far, there is no reliable fix available to solve the problem. Not all customers who did a clean install of OS X 10.11.4 or who purchased a new Mac are affected, and it is not clear if there is a pattern between users who are experiencing problems.

Article Link: Some Mac Users Unable to Log Into iMessage and FaceTime Following OS X 10.11.4 Update
[doublepost=1490302000][/doublepost]It's March 23, 2017. One year after this article was posted.

And I'm having the same problem. I love Apple.
 
[doublepost=1490302000][/doublepost]It's March 23, 2017. One year after this article was posted.

And I'm having the same problem. I love Apple.

Hi, masonsturtle I managed to fix it. Though loathed this with all my heart (the more so because it was 5th time I did all this "re-install" OSX magic in 24 months, 4 of which was the share of Lion reinstalls with 1 going to Mavericks) , seeking desperately for a solution and starting to suspect corrupted permissions at a deeper level, not within Disk Utility's scope of powers, I opted for the reinstallation of Lion on top of my existing files: this is the one advantage of Apple's "It just works" - it's the ease of installing and re-installing software. By "deeper level of permission corruption" I mean Access Control Lists that I might've have tweaked inadvertently causing confusion to the state of FaceTime: I remembered that trying to solve an issue with Disk Utility's inability to repair permissions I downloaded an exec file which was designed to remove ACLs and regretted doing this: on my part, having learned from such a bloody experience, I strongly recommend against any attempts of removing access control lists as it may lead to unexpected consequences and result in a disrupted functionality. After I reinstalled OS X the system automatically reset access control lists – not "permissions" which is overly simplified to becoming useless – and I regained the ability to use FaceTime again! You may want to follow my path and see what you get.

BTW, I was having a problem with iCal too, as it started behaving badly meaning that all alarms (sound alarms, mail alarms, display alarms) stopped showing up. I booted into Recovery mode, Launched Terminal from its menu bar's "Utilities" inset. In the appearing window, I selected my home folder (your username, that is), then I checked "Reset Access control Lists" at its bottom, it ran automatic reset operation and after a reboot iCal went back to life again.
 
Last edited:
Of all of the OS'es X I'm using I'm able to log in in Lion OS X. 2.5 years ago when I left my last post in this thread I ran Lion only however beginning with 2018 fall I lost FaceTime and have to use either iChat or Viber which still works with Lion. I'd prefer having it work in every of the OSes, though, because I still make of use of Lion a lot because it runs some older versions of the same apps better and has 32-bit support.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.