iMessage on my mac says every contact is not registered with iMessage

Since January 25th I'm experiencing the same issue - before everything worked just fine.

I tried all the trick described in this (and other) treats, including VRAM reset, removing com.* files, etc etc.

Eventually I thought it was related to the public beta which pushed 10.10.2 beta.

I erased my hard disk and reinstalled 10.10.1 clean.

Still the same effect, still not working,... and no useful help from Apple Support either :-(

So do I leave it at 10.10.1 and do the security update then wait for them to fix the imessage issue.

10.10.1 worked before so it should be possible to get back to a working state.

Do I really want to embark on getting 10.10.2 to work?

Thoughts?

I've been having this issue on my Mac for about a month on and off.

None of the fixes in this thread helped.

I've signed out and back into iCloud and separately out and into iMessage. I restarted with Command-R and verified and repaired disk permissions.

Even created a new User account to test with and same problem there.

iMessage works fine on my MacBook Pro, iPhone and iPad.

I just got off the phone with a Level two rep who is going to get back to me on Monday. He originally thought it might have to do with Keychain, will post again on Monday to let others know if this gets resolved.

FYI, there wasn't any fix on the iMessages server he could do. Sometimes people have their iMessage account locked, but that wasn't the case with me. Maybe that's what fixed it for others.

This problem started to happen out of nowhere. I have been on the phone with Apple care and a senior advisers. I have been dealing with this for 48 hours. I have done everything from sign out of iCloud - to resetting PRAM - dumping the plists. etc etc -- straight to wiping my hard drive clean and reinstalling yosmite and having to back up all my info. IT STILL DOES NOT WORK. as a side bar - I have made a TEST admin account and logged into my wife's messages and hers on same computer had no issues. I have done every step - it has to be something in the latest release and I just wish they would say that. I fear until Apple creates a patch, messages on my LAPTOP will simply not work as every contact i have is not registered with iMessage - even though they all were 4-5 days ago!!!!

HELP!!

Feel obligated to provide an update. I spent almost two hours on the phone with AppleCare and got elevated to Level 2 support. We did all sorts of logging in and out and resetting of settings, etc. and nothing seemed to work. Unfortunately, due to the amount of time I was on the phone, I had to go to another obligation and had to cut the call short. The AppleCare rep said he would continue to look into it and the next day everything started to work again. Not sure it it was all the steps I took on the phone with AppleCare that helped or if it was something that the rep. did offline after our call (resetting my ID or something) but whatever it was, I am now able to send and receive imessages to/from my iPhone, Mac and iPad; AND they all stay in sync. It's glorious! (Maybe a bit hyperbolic but it's nice to have it working again and it seems to have just restarted just as it stopped working.)

I was on the phone again yesterday with a level 2 advisor going over a multitude of things. No luck, they have to send it to engineering.

I will know more come Wednesday. I keep asking the techs if they know about re-setting the apple id at the messages server and no one seems to know what I'm talking about or that that is possible. Not sure what Ralph knows (or if that is ultimately what the engineers will do) but I am still a non functioning messages.

ONLY on my LAPTOP

Happy for you though

I have the same problem as well. I've tried everything. I can't believe Apple can't figure this out.

I believe this to be on the server side of iCloud. In my case, I had iMessage running on two Macs. When I looked at the settings on iCloud.com on my phone, it said that my other computer was a registered Mac with iMessage and not the one i'm currently using. I logged out on the other computer and my phone shows NO computer registered with iMessage, but iCloud.com still shows my both computers there.

What I think is happening is I'm trying to send messages from a computer that is not properly registered with my iMessage/iCloud account - it won't let me send therefore all the addresses turn red. I think iMessage/iCloud service still thinks my other computer is the Mac that is authorized to send. This suggests that only one Mac computer can be authorized. Because I authorized two, it has screwed everything up.

As an update - the issue has been moving up the chain at the corporate level. it's been over a week since my first claim with no fix. But I got a call from Apple yesterday asking me questions about my contacts and setup etc. It's still not fixed but they are going to get back to me. At least I know we are not crazy - they are aware of this issue and they are working on it. and there is nothing we can do on our end - so stop the madness in trying. I'll update you all when I know more.

Tried that; didn't work

iMessage worked last sunday; problems started on monday and is still ongoing.

live in the Netherlands and tried from every angle to get it working.

Its got to be a server problem, because on my iphone it works.

It really baffles me

iMessage works for some of my contacts, from my MacBook Pro running OS X 10.9.5, but not all of them; I have never had any problems, however, messaging any of my contacts from my iPhone 6.

Obviously nothing is "fixed", wherever the problem is originating.

I just solved my issue.

Hope it works for others.

Just to clarify, I wasn't able to send iMessages on my Mac without the not delivered red exclamation mark symbol.

I searched for Keychain Access in Spotlight, and deleted everything in "All Items" that had iMessage, and/or Apple in the keychain.

I rebooted my Mac, and after that, I was able to send from iMessage with no problems.

I hope it works for others.

I have just had a similar issue as well. My Mac Mini no longet seems to register iMessage. All of my contacts now show as not being registered with iMessage and the Mac no longer appears in SMS forwarding on my iPhone. I have an iPad and MacBook and both are fine. I have tried deleting my Keychain, doing a complete reinstall, signed out of iCloud and iMessage on all my devices, but still no luck. Did anyone get this working in the end. I installed OSX 10.10.3 beta as a VM in parallels on my Mac Mini and the issue seemed to appear after this.

Just an update. I have been in contact with Apple Support and it has now been raised to their level 2 support and passed to an engineering team. I have also noticed that handoff is no longer working across any of my devices as well. Have you noticed this? I'll add updates when I hear more.

Same here. Spoke with Level 2. Waiting for them to contact back. Case # Assigned. They tried to send a screen share via iMessage platform and of course it failed.

Yep, Continuity broken across all devices. i'm left with whatever i had in handoff before this started. Changes don't propagate between iPhone and iPad or MBPR & MBP.

iMessage still works though on everything else.

They did confirm that a fresh install would not resolve this.

Just wanted to confirm "cause" in case someone is looking for the root of all of this...

I got myself into the same state as everyone else on this thread, and started down the path with Apple Support (haven't gotten to level 2 yet ;-) ) who had me reset PRAM, re-install OSX, and try a restore from previous time machine back-up, all to no avail.

When I saw your post regarding a parallel's VM, it all clicked. I, similarly, have a vmware VM running OSX that I started up yesterday, and that is when all of the goofiness started for me. I don't think it's a coincidence YFInder! I will run down your list this evening and report back whether it worked for me too. If there's a particular order, or methodology that you would like me to try, let me know.

I also noticed that FaceTime will not call out or receive incoming calls correctly, although there is nothing indicating that it is not functioning properly.