High Sierra won't send iMessages

Hi IBG,

In another thread (I referred to in this thread), the following worked for me:

1) Close the Messages App

2) Open Key Chain Access

3) Select your main keychain (usually the user name) at the top left side

4) Select "All Items" on the lower left side

5) Search for entries of "IDS"

6) Highlight and delete all entries that has IDS.

7) Search for entries of "FaceTime"

8) Highlight and delete all entries of FaceTime

9) Search for entries of "Messages"

10) Highlight and delete all entries of Messages

11) Reboot

Optional 12) Test it out. If it doesn't work, zap the PRAM a couple of times, then try again.

It was scary because it mentions something about not being able to open previously received chats, but I found the was not the case. I did it and it cleared up the problem for me. I had A LOT of old Message Encryption and Signing keys. Probably some old ones were incompatible or one of them was corrupted. Hope this helps.

r/Jim

I talked to apple chat support and they had me reset the PVRAM.

1: Shut down your computer.

2: Immediately after powering on, Hold down Command+Option+P+R until you hear the second startup chime.

I had to do it twice but it worked. Messages are sending just fine now.

LogOut of your iCloud accounts, Messages;

Go to system preferences;

Then sign out:

Go to Messages preferences then click accounts, then sign out:

--- sign out >>>>

Open FaceTime and make sure it's not logged in...

Now, AFTER you've made sure you're logged out - Reboot or Power off computer, then allow it to boot back up and turn on these settings - it wouldn't hurt if this does not fit it to do a safe boot then retry, or you can do a safe boot next then boot back normally then turn on your iCloud accounts and log back in... Either way, make sure you boot before you try to enable the iCloud again.... I've fixed so many problems this way that just switching on and off would not repair, now it is my go to first step.

Good troubleshooting guide for this issue here. I did nearly all of the things suggested, and even sent logs in to Apple Support for further investigation.

Ultimately, what worked for me was to run this command from Terminal:

sudo rm /Library/Preferences/com.apple.apsd.plist

Hi,

In that case work through this Users Tip When the iMessages account will not Login

If you have to ring Apple there are things to remember:-

1) it will t sake a while.

2) Level 1 responders are looking are Apple Case issues.

3) Apple IDs are free to fix.

4) you have to get high enough up the chain to be able to get the person to actually check the server.

AS each device uses the Serial Number to identify itself the Block can be Device Specific. This means the ID may work in iTunes and the App Store and only Not Work on the Mac for iMessages.

8:19 pm Friday; September 29, 2017

Thank you s0s4help!

I have proceeded by deleting several entries (perhaps 20 or 30 in total) from the iCloud keychain referring to Messages.app or Apple or iCloud etc.

After so many days of failed attempts, this has solved the problem. I will also report to the Apple service in Germany, which is still looking for a solution.

I had this problem after upgrading to HS, tried loads of stuff such as signing out / in and deleting items in keychain but nothing worked. In the end I signed out of iMessage, restarted, then zapped the PRAM (CTRL,OPT,P,R) and then signed in to find it working.

Hope this helps.

Did you try this?

1: Shut down your computer.

2: Immediately after powering on, Hold down Command+Option+P+R until you hear the second startup chime.

That's what I did and it worked like a charm! Thanks to Seandiego!

Hi All I have solved restarting and resetting the NVRAM (reboot with option + cmd + p + r)

Try to log back into your apple account. One time a random window popped up asking me to log into my apple account and that solved my problem.

Restarting he computer after deleting all that keychain info helped.

Zapping the PRAM fixed it for me! I tried deleting keychain entries which did not help.

Thank you! I zapped the PRAM & that solved it for me!