1 3 4 5 6 7 Previous Next 153 Replies Latest reply: Dec 21, 2013 2:12 PM by Paul J. Hart Go to original post Branched to a new discussion.
  • 60. Re: iMessage login issues
    Prometheus 7 Level 1 Level 1 (30 points)

    Hi everyone!

    It's a bit late, but something that worked for me was to go to the time preferences to uncheck and recheck the automatic date and time setting. I remembered that I had set the time manually because of a weird router, but the box was checked when I looked. Before I did it, iMessages didn't work, and immediately after, it did. Not sure why! If you could help me make some sense of this, Ralph, that would be great, but mostly I'm just happy it's working.

  • 61. Re: iMessage login issues
    Time2rideaz Level 1 Level 1 (10 points)

    I had this issue also. Turns out it was an untrusted certificate in my keychain. I deleted it and iMessage and Facetime logged right in. The certificate was for the iPhone Configuration Utility, which was loaded to trouble shoot the original iPad's battery drain issue, then deleted but I guess the certificate stayed behind and was no longer trusted.

  • 62. Re: iMessage login issues
    Ralph Johns (UK) Level 9 Level 9 (67,505 points)

    Hi Prometheus,

     

    I now about the Date & Time issue.

    Both FaceTime and Messages/iChat send Time stamped item to stay in sync with the Buddy during chats (A/V) or add the info in Text chats.

     

    It is also used in some of the Login process as it is used to Identify the time where you are and that of your Buddy to make sure Time Zones are accounted for with long distance east to west chats (or west to east)

    (It used to calculate how many "hops" (routers) you may pass-through on the Internet to get through to a Login or a Buddy - With IP 4 you should never be more than 64 hops away from anybody but iChat and Messages have a 6 hop margin built in (Allows for LAN routers as well then) )

     

    If you are out of sync with the rest of the world either in the Mac Settings  or in your routing device you will have problems.

     

    As Time2rideaz says it is more likely to be a corrupt bit of info that is the issue.

     

     

     

     


    10:30 PM      Saturday; July 28, 2012


    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

     

      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),

    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • 63. Re: iMessage login issues
    chaser7016 Level 1 Level 1 (0 points)

    To fix try this.....

     

    At the top right click the day and time --> Choose "Open Date & Time Preferences," and make sure that "Set date and time automatically" is checked.

     

    If it's not your not synced up with Apple servers, thus causing the error to appear.

  • 64. Re: iMessage login issues
    Slosteve Level 1 Level 1 (0 points)

    Hi,

     

    I have read through the thread and nothing seems to work for me

    I actually get (translated from Swedish): "Couldn't login. Check your network connection and try again."

    Everything else works just fine except for iMessage. I did install the ML so it is not the iMessage Beta.

     

    One thing I noticed in system.log was this after trying to login: "Jul 31 11:18:13 ********.local apsd[87]: Certificate not yet generated"

    There is more, but I don't know that info is needed?!

     

    I'm on a corporate network with password proxy and all that stuff...

     

    Any ideas?

     

    BR,
    Stefan

     

    Here is the rest from the logfile:

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] Someone tried to delete a phone account, you can't do this

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 1   IMFoundation                        0x00007fff941edd62 IMLogBacktraceToDepth + 69

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 2   IMCore                              0x00007fff8defe773 IMPersonStatusComparator + 97511

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 3   IMCore                              0x00007fff8defe711 IMPersonStatusComparator + 97413

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 4   iMessage                            0x000000010ea14bf2 -[iMessagePreferences _clearAccountKeepingLogin:] + 604

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 5   iMessage                            0x000000010ea1438c -[iMessagePreferences _authenticationTimerTimedOut:] + 128

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 6   CoreFoundation                      0x00007fff89319cac __invoking___ + 140

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 7   CoreFoundation                      0x00007fff89319b47 -[NSInvocation invoke] + 263

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 8   Foundation                          0x00007fff9075a743 __NSFireTimer + 96

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 9   CoreFoundation                      0x00007fff892e34b4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 10  CoreFoundation                      0x00007fff892e2fcd __CFRunLoopDoTimer + 557

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 11  CoreFoundation                      0x00007fff892c87b9 __CFRunLoopRun + 1513

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 12  CoreFoundation                      0x00007fff892c7dd2 CFRunLoopRunSpecific + 290

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 13  HIToolbox                           0x00007fff88fc2774 RunCurrentEventLoopInMode + 209

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 14  HIToolbox                           0x00007fff88fc2512 ReceiveNextEventCommon + 356

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 15  HIToolbox                           0x00007fff88fc23a3 BlockUntilNextEventMatchingListInMode + 62

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 16  AppKit                              0x00007fff936ddfa3 _DPSNextEvent + 685

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 17  AppKit                              0x00007fff936dd862 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 18  AppKit                              0x00007fff936d4c03 -[NSApplication run] + 517

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 19  AppKit                              0x00007fff93679656 NSApplicationMain + 869

    Jul 31 11:39:16 *****.local Messages[762]: [Warning] 20  libdyld.dylib                       0x00007fff9138d7e1 start + 0

    Jul 31 11:39:16 *****.local apsd[87]: Certificate not yet generated

    Jul 31 11:39:46 *****.local apsd[87]: Certificate not yet generated

     

    Message was edited by: Slosteve

  • 65. Re: iMessage login issues
    Ralph Johns (UK) Level 9 Level 9 (67,505 points)

    HI,

     

    As this is a case where a Proxy is used it will be  slightky different issue.

     

    That is not to say that the two are not closely related.

     

    Also iChat never really worked when a Proxy was being used and Messages still uses the iChat "Engine"

     

     


    8:07 PM      Tuesday; July 31, 2012


    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

     

      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),

    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • 66. Re: iMessage login issues
    Slosteve Level 1 Level 1 (0 points)

    Hi,

     

    This is actually not a proxy issue, after further digging. When I connect my MacBook Air to another network, without proxies and firewall, I still get the same error message.

     

    Is it possible to restore or reinstall just the iMessage app? Just to see if this helps.

    And that "Certificate not yet generated", sure is something I need to figure out. Since this message only ends up in the system.log when I try login.

     

    Any ideas would much appreciated!

     

    /Stefan

  • 67. Re: iMessage login issues
    Ralph Johns (UK) Level 9 Level 9 (67,505 points)

    Hi,

     

    I am not sure that the "recovery" Process can drill down to single Apps

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


    9:31 PM      Wednesday; August 1, 2012


    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

     

      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),

    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • 68. Re: iMessage login issues
    Ralph Johns (UK) Level 9 Level 9 (67,505 points)

    HI,

     

    In the Finder go to the Go Menu and then Hold down the ALT key

    Select the Library that you can now see.

    Open Preferences

    Find com.apple.imagent.plist and drag it to the Trash

    Restart Messages.

     

     

     

     


    9:36 PM      Wednesday; August 1, 2012


    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

     

      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),

    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • 69. Re: iMessage login issues
    stevefromtorquay Level 1 Level 1 (0 points)

    I have spent days on this following Ralph's kind advice.

     

    I couldn't get into twitter, messages or facetime.  What fixed it for me was checking the automatically date and time

     

    At the top right click the day and time --> Choose "Open Date & Time Preferences," and make sure that "Set date and time automatically" is checked.

  • 70. Re: iMessage login issues
    BTMUSN Level 1 Level 1 (0 points)

    I am currently stationed in Guam and had forgot about manually changing my time too. I have been going through so many steps trying to figure out why my Imessage wouldnt register my primary apple ID. Thank you so much for your post. Thats exactly what my issue was.

  • 71. Re: iMessage login issues
    Ciarrach Level 1 Level 1 (0 points)

    I registered and logged-in to Apple Support Communities and hey presto, iMessage and Facetime registration errors disappeared.

     

    Its worth a try.

  • 72. Re: iMessage login issues
    Ralph Johns (UK) Level 9 Level 9 (67,505 points)

    Hi,

     

    Thanks for letting us know.

     

     


    8:43 PM      Monday; August 6, 2012


    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

     

      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),

    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • 73. Re: iMessage login issues
    joesoes Level 1 Level 1 (50 points)

    I have the same issue. I just cant log into iMessage on my mac. My Apple-ID is OK and works fine on my iPhone, iPad and my Mac on Facetime.

     

    I´ve tried to remove the com.apple.imagend.plist but it did not help.

     

    Any ideas? My DNS is set to Googles DNS 8.8.8.8 since a long time ago.

  • 74. Re: iMessage login issues
    Matthew L. Smith Level 1 Level 1 (75 points)

    Did you try entering your apple ID as @mac.com instead of @me.com?  That's what got things working for me.  Also, if you upgraded to Mountain Lion, you're entitled to either 30 or 90 days of free phone support.  Maybe an Apple support person can help you on the phone.  I was having a problem with my System Preferences locking and refusing to unlock, and they were able to help me with it.  They were great to work with too.

1 3 4 5 6 7 Previous Next