the blue

Q: Messages Not Working in Mavericks 10.9

Hi there,

 

Anyone else having this problem?   My Messages is just not working.  I am logged in.   It lets me type a message, but then it just sits there and a few minutes later I get the red circle/ "!" saying it didn't go through.  I've tried logging in and out of Messages.  Restarting the computer of course.  Nothing.  I'm stuck.  I can't find another post on this so anyone else having this issue?

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Oct 31, 2013 8:29 AM

Close

Q: Messages Not Working in Mavericks 10.9

  • All replies
  • Helpful answers

Previous Page 2 of 5 last Next
  • by Michael Hoffman,

    Michael Hoffman Michael Hoffman Nov 5, 2013 5:05 AM in response to the blue
    Level 1 (80 points)
    Nov 5, 2013 5:05 AM in response to the blue

    ...and just to test, I logged out and logged into Messages under my daughter's Apple ID and still can't send iMessages. Somewhere there must be a user plist file or something specific to this user's home folder that is breaking this.

  • by Michael Hoffman,Helpful

    Michael Hoffman Michael Hoffman Nov 5, 2013 7:20 AM in response to the blue
    Level 1 (80 points)
    Nov 5, 2013 7:20 AM in response to the blue

    Ok, I finally got it. If none of the other things do it for you and you're getting the same errors I was, try resetting your keychain

     

    http://support.apple.com/kb/ts1544

     

    Repairing didn't help me, as it didn't show any errors, but resetting it did the trick.

     

    I would like to add though that it's not perfect, as it's showing the red exclamation point for a second, then it disappears again, then it says delivered. This is also happening on my Air and iPhone now, as well as on my wife's iPhone. Console shows this one lone error each time an iMessage sends:


    identityservicesd: [Warning] Could not find public identity for token: ...

     

    This may or not be related to the original problem, but I wanted to throw it out there.

  • by amg229,

    amg229 amg229 Nov 5, 2013 11:13 AM in response to Michael Hoffman
    Level 1 (0 points)
    Nov 5, 2013 11:13 AM in response to Michael Hoffman

    Resetting the keychain fixed mine. THANK YOU!

  • by Michael Hoffman,

    Michael Hoffman Michael Hoffman Nov 5, 2013 11:18 AM in response to the blue
    Level 1 (80 points)
    Nov 5, 2013 11:18 AM in response to the blue

    Great! The secondary issue after the fact (the quick appearing and disappearing of the exclamation point), was actually happening from ALL of my devices as well as to anyone on an iPhone or mac that was sending an iMessage TO me. I fixed that issue by changing my apple ID password.

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 5, 2013 12:49 PM in response to the blue
    Level 9 (73,336 points)
    Applications
    Nov 5, 2013 12:49 PM in response to the blue

    Hi,

     

    I see below that one of the other posters tried a Keychain reset.

    Have you tried this ?

     

     

     

    3Sigcopy2.png
    8:49 pm      Tuesday; November 5, 2013

     

      iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     Couple of iPhones and an iPad

  • by the blue,

    the blue the blue Nov 5, 2013 4:16 PM in response to Michael Hoffman
    Level 1 (0 points)
    Nov 5, 2013 4:16 PM in response to Michael Hoffman

    Thanks Michael for this.

     

    Sadly, I did this twice and no dice.  I still have the same issues (imessages working on my mobile devices, messages not going through either way on my laptop).

     

    Jason

  • by Michael Hoffman,

    Michael Hoffman Michael Hoffman Nov 5, 2013 5:30 PM in response to the blue
    Level 1 (80 points)
    Nov 5, 2013 5:30 PM in response to the blue

    Open your console log. When you hit send on an iMessage and it fails, what types of errors is it registering? That's how I figured out the keychain problem. This might at least give you an idea of what TYPE of problem you're having, and you can dig in the right direction like I did for myself.

  • by the blue,

    the blue the blue Nov 5, 2013 9:38 PM in response to Michael Hoffman
    Level 1 (0 points)
    Nov 5, 2013 9:38 PM in response to Michael Hoffman

    Ah good idea Michael.  I rarely go 'under the hood'   This is what immediate popped up when I try to send a message:

     

    Thoughts O Community?  Obviously I have 'trust' issues - but not just how to solve them!

     

    Jason

     

     

    11/5/13 9:36:16.681 PM xpcproxy[526]: assertion failed: 13A603: xpcproxy + 3438 [EE7817B0-1FA1-3603-B88A-BD5E595DA86F]: 0x2

    11/5/13 9:36:16.744 PM apsd[80]: Failed to evaluate trust: No error. (0), result=5; retrying with revocation checking optional

    11/5/13 9:36:16.747 PM apsd[80]: failed to evaluate trust: No error. (0), result=5; retrying with system roots

    11/5/13 9:36:16.750 PM apsd[80]: Root certificate is not explicitly trusted

    11/5/13 9:36:16.751 PM apsd[80]: Untrusted peer, closing connection immediately

    11/5/13 9:36:16.929 PM apsd[80]: Failed to evaluate trust: No error. (0), result=5; retrying with revocation checking optional

    11/5/13 9:36:16.931 PM apsd[80]: failed to evaluate trust: No error. (0), result=5; retrying with system roots

    11/5/13 9:36:16.934 PM apsd[80]: Root certificate is not explicitly trusted

    11/5/13 9:36:16.934 PM apsd[80]: Untrusted peer, closing connection immediately

    11/5/13 9:36:17.109 PM apsd[80]: Failed to evaluate trust: No error. (0), result=5; retrying with revocation checking optional

    11/5/13 9:36:17.111 PM apsd[80]: failed to evaluate trust: No error. (0), result=5; retrying with system roots

    11/5/13 9:36:17.114 PM apsd[80]: Root certificate is not explicitly trusted

    11/5/13 9:36:17.114 PM apsd[80]: Untrusted peer, closing connection immediately

    11/5/13 9:36:17.284 PM apsd[80]: Failed to evaluate trust: No error. (0), result=5; retrying with revocation checking optional

    11/5/13 9:36:17.288 PM apsd[80]: failed to evaluate trust: No error. (0), result=5; retrying with system roots

    11/5/13 9:36:17.291 PM apsd[80]: Root certificate is not explicitly trusted

    11/5/13 9:36:17.291 PM apsd[80]: Untrusted peer, closing connection immediately

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 6, 2013 12:09 PM in response to the blue
    Level 9 (73,336 points)
    Applications
    Nov 6, 2013 12:09 PM in response to the blue

    Hi,

     

    11/5/13 9:36:16.681 PM xpcproxy[526]: assertion failed: 13A603: xpcproxy + 3438 [EE7817B0-1FA1-3603-B88A-BD5E595DA86F]: 0x2

     

    The 13A603 is the Build number of the OS X 10.9 general release.

    (Go to the Apple Icon Menu and then About this Mac.  Click on the current OS X version line and it changes to the Build number).

     

    I have seen people post about the System Preference > Network holding some Info about the Proxy set to being Automatic.

    System Preferences > Network > Advanced Button > Proxies tab top item in list.

    Screen Shot 2013-11-06 at 20.02.33.png

     

    As to the apsd item that seems to be listed as having a PID or 80 (See Activity Monitor set at All Processes)

    Screen Shot 2013-11-06 at 20.05.51.png

    I am not sure what the apsd stands for and could not tell if the peer is the connection to the Server (therefore the proxy is not trusted) if it is referring to a Buddy or Contact depending if it it is an iChat type Chat or iMessage conversation.

     

    I am leaning towards it being linked to the Proxy thing.

     

     

     

     

     

     

    3Sigcopy2.png
    8:09 pm      Wednesday; November 6, 2013

     

      iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     Couple of iPhones and an iPad

  • by SBinthe425,

    SBinthe425 SBinthe425 Nov 18, 2013 11:35 AM in response to Michael Hoffman
    Level 1 (0 points)
    Nov 18, 2013 11:35 AM in response to Michael Hoffman

    Resetting the keychain worked for me.  Thanks!

  • by the blue,

    the blue the blue Nov 18, 2013 8:38 PM in response to Ralph Johns (UK)
    Level 1 (0 points)
    Nov 18, 2013 8:38 PM in response to Ralph Johns (UK)

    Hi - I'm still stuck.  I even reinstalled Mavericks.   How would I solve it if its a proxy thing?

     

    Thanks for the help!

  • by nearp,

    nearp nearp Nov 19, 2013 10:34 AM in response to the blue
    Level 1 (0 points)
    Nov 19, 2013 10:34 AM in response to the blue

    Hey everyone.  After digging up some other support discussions about this issue I found the one that worked for me.

     

    I had recently had my logic board replaced.  This erased me serial number and the genius team did not assign a new one.

     

    Check in about this Mac>more info. Make sure you still have a serial number.

     

    If it's gone, just take to apple store and they will fix it.  Takes about 15min.

     

    Hope that helps some of you!

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 19, 2013 2:37 PM in response to the blue
    Level 9 (73,336 points)
    Applications
    Nov 19, 2013 2:37 PM in response to the blue

    Hi,

     

    In my pic above there is nothing in the Auto item at the top of the Proxies list.

    Some people seemed to be saying their's was ticked and this was the issue.

    If you don't use a Proxy to connect to the internet then delete any settings in this pane.

     

     

    3Sigcopy2.png
    10:37 pm      Tuesday; November 19, 2013

     

      iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     Couple of iPhones and an iPad

  • by DrFooMod2,

    DrFooMod2 DrFooMod2 Nov 24, 2013 6:46 AM in response to Michael Hoffman
    Level 1 (4 points)
    Servers Enterprise
    Nov 24, 2013 6:46 AM in response to Michael Hoffman

    Just as an add-on for others, not only did resetting the keychain make Messages work, but I was also having an issue with Mail, and this fixed that too. Thanks!

  • by macuserdrew,

    macuserdrew macuserdrew Dec 2, 2013 3:43 PM in response to Ralph Johns (UK)
    Level 1 (0 points)
    Dec 2, 2013 3:43 PM in response to Ralph Johns (UK)

    Ralph,

     

    I've been trolling through these fixes for a couple days now. I have a MacBook Pro from 2010. I have installed all operating system updates as soon as they've been released for as long as I've owned it. About a month after installing Mavericks, my iMessage stopped working. I cannot sign in to my iMessage account at all, much less attempt to send a message. I have tried the following: removing alternative email addresses from my apple id, changing my apple id and logging back in, signing out from icloud and imessages on all of my apple devices (imessage works great on my iphone running ios 7 by the way), reset the keychain (which I had not activated through iCloud yet, as I use 1password), enabling and disabling icloud keychain on all my devices.

     

    The errror message is the standard "cannot sign in, please check your network connection" but it has varied and I have also encountered one along the lines of "The user name or password was incorrect. Try again.". This particular message tends to appear multiple times, even after I repeatedly dismiss the message. Typically the box will appear five times. After I dismiss the fifth box occasionally the messages app seems to have recognized my information (it provides me with my phone number and the email address associated with my id and the option to enable imessage). This view disappears within two seconds, except one time when I managed to click a setting and it hung around for as long as it took me to realize that it wasn't actually enabled and I logged out again.

     

    This problem is extremely frustrating. Any help would be appreciated as I have no warranty coverage on my machine for service calls.

Previous Page 2 of 5 last Next