iMessage/Face Time on OSX 10.11.4

Same problem here. Tried fresh install of both 10.11.3 and 10.11.4. Upon first boot, logging in with Apple ID only causes my Mac to hang. Restarting and skipping the Apple ID lets me on the computer. Within system preferences I am able to log in to my iCloud account but the following still do not work or allow me to log in, iMessage, FaceTime and the app store.

Logging in to these apps causes them to hang and nothing happens. Curiously though, purposely entering the password incorrectly generates the "invalid password" message so its not a connectivity issue but when entering correct password it just sits there.

Was told by Apple Care senior advisor that she is checking with engineers on a status update and would get back to me. IF and that's a big IF, she ever does provide a status, I will be sure to chime in here 🙂

I have the same problem. Can confirm I see Certificate not yet generated messages non-stop as well.

Same problem here.

Only way to prevent the logs to display "apsd: Certificate not yet generated" is to disable APSD (Apple Push Notification Service Daemon). And of course, this is not a solution.

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.apsd.plist

I don't know what happen but I think the FaceTime-part is fixed now. Still waiting for iMessage to be fixed.

Every one with new macs and clear install have that problem, right now how I can see, Apple iCloud Servers cannot generate certificate to continue authentication, so we have to wait till they fix their servers.

Good news, seems everything is OK now.

I can login now on my Macbook and send iMessages \0/

Yes its working again for me also

Ok now I message and FaceTime finally logged in, error message gone from console, but now I have no iMessage settings,

any ideas?

hi,

Seems it might be a temporary issue http://www.apple.com/support/systemstatus/

Scroll the Time Line back.

9:56 pm Thursday; March 24, 2016

PRAM reset. But first... sign out of iCloud... then De-Authorize computer... then do a PRAM reset (Here's how...) shut down... as in... SHUT-DOWN... then power on button... followed IMMEDIATELY... by simultaneously holding down "Option", "Command","p-key", and "r-key"... PRACTICE HOW YOU WILL PLACE AND HOLD YOUR FINGERS FIRST... before starting cycle... easy... but will save a redo... to practice position before starting... To be absolutely sure it's a reset... hold it until the 5th start-up Chime and release then and let it reboot normally... THEN sign into iTunes and Re-Authorize computer... Then sign into iMessages in system preferences... Then sign into to iMessage... forget about clean installs and all that unless you want one for other reasons. This should work for those who had this iM issue when you upgraded to 10.11.4 It will likely continue in 10.11.5 without a pram reset

Humm,

PRAM reset (CMD+ALT+P+R) is for PowerMac computers using chips before Intels were used.

It is the same keys but referred to as NVRAM reset now

How to Reset NVRAM on your Mac - Apple Support

These Apple Documents are always being updated and I am sure that in the PowerMac days it was Three Bongs that were needed and not the two they state now.

I am still note sure that waiting for 5 is going to gain anything.

As iMessages and FaceTime are on their own Servers I don't see the benefit of signing out of iTunes to the point of De-authorising the computer

iTunes is on a completely different server. (you can be blocked at iMessages and not iTunes)

I like to know how you did this bit:-

Then sign into iMessages in system preferences...

In System Preferences you have Internet Accounts and iCloud panes.

In the iCloud one there is nothing about iMessages (or Messages), FaceTime, iTunes, App Store, iBooks, Developer (if you have an account).

I.e. you cannot login to iMessages for the iCloud pane (nor any of the other I listed)

In Internet Accounts you might have an Apple ID listed as A Valid AIM Screen Name Login

This still will not login iMessages.

10:03 pm Saturday; May 28, 2016

Hello, are you having this imessage error issue... yourself... currently?

Hi,

No.

However I read the whole of the iChat Forum filtered as Content so I can see which I have read and those I have not.

Same with Mountain Lion area tagged with Messages.

And again with Mavericks

And Yosemite and El Capitan

At one time iChat was two separate forums for iChat 1 and 2 and for the versions above that

At Snow Leopard the iChat (5) was a separate section within the Snow Leopard area Mac OS X v10.6 Snow Leopard

This is about 360 pages on what I know about iChat http://www.ralphjohns.co.uk/

Whilst there are some posts that are in Mountain Lion and above that are not tagged by the Poster as being about Messages or iMessages I do read and in most cases answer the posts that are.

I have been using Macs since 1991 and have owned one since 1992 when I purchased a Performa 400 (it still works) Running System 7.3.x.

Since then I have had an Original Bondi Blue G3 iMac (the Bubble shaped one) A G4 tower 1Ghz Mirrored Doors that I still turn on every day and use to test iChat 4.0.9 in Leopard, a Macbook Pro running Snow Leopard from 2006 and my current iMac from 2011.

There are some Continuity and Handoff things my Mac will not do.

So it means I do have the practising knowledge that most of what you posted is misleading to say the least.

9:22 pm Sunday; May 29, 2016

I have the same problem. El Capitan 10.11.6. When I try to start Messages it says it can't log into iCloud because of "a problem with the iCloud account" Then it invites me to fix it in iCloud system preferences. However, when I go there it says my password "needs to be updated" and when I key in my correct password it says "an unknown error occurred".

I've been round this loop multiple times and I've even updated my password. I can log in to iCloud fine on both the iPhone and the Mac; however Messages and Facetime both refuse to accept my login credentials. iMessage and Facetime are both properly activated on the iPhone and I can make calls/messages with both of them on the iPhone.

I think this may possibly have started when I did an iPhone update to 9.3.3 but not 100% sure.

Hi,

Re: iMessage

7:39 pm Tuesday; August 2, 2016