jkheit

Q: Messages.app/Facetime Broken/Not-Working in Yosemite 10.10

Hi all.

 

I'm wondering if anyone else is having a problem with Messages.app/iMessage/Facetime after upgrading/installing Yosemite (the release version)? My Messages doesn't work.

 

The Problems

(A) Specifically, when you enter your AppleID in Messages.app->Preferences->Accounts->iMessagesAccount you get the following error:

 

 

Quote:

 

Could not sign in to iMessage.
Could not sign in. Please check your network connection and try again.
Sometimes the error says it cannot activate.

 

(B) Also, oddly, FaceTime makes me enter my AppleID every time i reboot, but will work for Video FaceTime chats, but not audio?  And once I reboot, it again asks me for my AppleID.

 

My Setup

 

 

I have a 2010 Mac Pro.

 

My Mac Pro is not stock, but nothing that's in there *should* cause a problem, so I wonder if anyone else is having a similar issue. My non stock hardware is:
  1. --MacVidCard 802.11ac and bluetooth 4.0 upgrade card (http://www.macvidcards.com/store/p33...port_Card.html)
  2. --VisionTek 7750 Eyefinity 6 2GB card (https://www.visiontek.com/graphics-c...rd-detail.html)
  3. --OWC Mercury Accelsior E2 SSD (http://eshop.macsales.com/shop/SSD/P...Accelsior/RAID)
  4. --Inateck 4 port PCI-E to USB 3.0 card (which has requires no drivers and is a pretty compatible card) (http://www.inateck.com/inateck-kt400...er-connection/)
  5. --Upgraded the 12-core 2.66ghz motherboard to 12-core 3.46 west mere x5690 xenon (turnkey OWC upgrade) (http://eshop.macsales.com/shop/turnk...Xeon_Processor)
Here is some of the troubleshooting I've already done:
  1. I tried making a new guest account and tried to login there, and went so far as to install a clean install on a blank external drive with similar results.
    1. The only caveat is when you make the new guest account of fresh install, when you first put in your AppleID it almost kinda succeeds.  You initially see the screen where Messages tells you it's associating your phone number and a few email addresses together.  But if you try to use Messages, nothing gets through, and when you quit and re-run the app, you get that same 'could not sign in' error.
  2. Went through the stuff here to no avail:
    1. messages "An error occurred while activating. Try again later"
  3. My serial number does show in about this Mac.
  4. Messages/iMessage/Facetime all work(ed) fine under 10.9.x on the Mac Pro, so it should not be a hardware issue, as I didn't change any hardware over after upgrading.
  5. I installed Yosemite on my 2013 13" Macbook Pro and Messages/Facetime all work fine, so it's likely nothing to do with my network.
  6. I have confirmed that others that have done the MacVidCard 802.11ac/bluetooth upgrade are not experiencing this issue.
  7. Same with the USB card.
  8. Since I installed a fresh OS on an external drive, I doubt the OWC Accelsior has anything to do with this.
  9. I called apple support, and they are stumped and getting engineers to figure it out. One support guy at apple said the broken Messages.app problems were his only unresolvable problem he was getting this since Yosemite launched (and that it has been an exceptionally smooth launch), and had 4 calls on the same issue early morning the day after launch (he's one level up from the entry support folks and the only level above him are the actual software engineers).
  10. The video card seems highly unlikely to matter here. Then again, I'm not sure the hardware should matter at all...Which leaves me with...


My Suspicion

 

 

I think there may be an interplay between 2 things going on.  One, although I haven't changed my motherboard, perhaps changing the processor tray makes something fail with the Messages authentication?  And second, perhaps there is some corrupted data up on iCloud that alone or in combination with the processor tray, is tripping up Messages verification? The solution might be to bring my machine in and have them do some magic to make the serial number authorized on their system?


Appreciate any thoughts and thanks for any help. Thanks!

 



Posted on Oct 18, 2014 2:27 PM

Close

Q: Messages.app/Facetime Broken/Not-Working in Yosemite 10.10

  • All replies
  • Helpful answers

first Previous Page 6 of 8 last Next
  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 20, 2014 11:13 AM in response to kadavr
    Level 9 (73,336 points)
    Applications
    Nov 20, 2014 11:13 AM in response to kadavr

    Hi,

     

    Use the Font Book app to check the AppleGothic Font (It appears as all one word and is well down the list in the app).

    Check it validates (File Menu), as Active (does not say Disabled) and is not duplicated.

     

    This font is needed to start up the app.

     

     

     

     

    3Sigcopy2.png

    7:13 PM      Thursday; November 20, 2014

     

      iMac 2.5Ghz i5 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 Toby DeVoss,

    Toby DeVoss Toby DeVoss Nov 20, 2014 3:40 PM in response to Ralph Johns (UK)
    Level 1 (5 points)
    Mac OS X
    Nov 20, 2014 3:40 PM in response to Ralph Johns (UK)

    Ralph!!! You are my new hero! Where can I send the flowers? (Don't worry ...I'm female.)

     

    Seriously, I had looked for AppleGothic and it showed "active" by default in the system ....but, you are right, a little further down the list is yet another AppleGothic. After activation, Messages appeared.

     

    Many, many thanks!

  • by kadavr,

    kadavr kadavr Nov 20, 2014 5:05 PM in response to Ralph Johns (UK)
    Level 1 (0 points)
    Nov 20, 2014 5:05 PM in response to Ralph Johns (UK)

    Thanks Ralph,

     

     

    At least it helped the topic starter, but in my fonts list AppleGothic is the on, only, validatable and active.

     

    It wasn't Messages that didn't start, it was the welcome screen of them that never showed up earlier before I killed the process and relaunched it back.

  • by jkheit,Solvedanswer

    jkheit jkheit Nov 20, 2014 5:08 PM in response to jkheit
    Level 1 (4 points)
    Nov 20, 2014 5:08 PM in response to jkheit

    So the solution after all this?  Reset parameter RAM.  Try it twice if it doesn't take.  I tried it before, maybe I did something weird, maybe the 10.10.1 update made some difference.  But resetting my parameter RAM and rebooting did the trick

     

    To reset parameter RAM, just boot and hit COMMAND-OPTION-P-R simultaneously before the grey boot screen comes up, and keep it pressed until you hear the 2nd system reboot BONG sound and then let go.

     

    Hope this helps the rest of you fellas!

  • by kadavr,

    kadavr kadavr Nov 21, 2014 4:21 AM in response to jkheit
    Level 1 (0 points)
    Nov 21, 2014 4:21 AM in response to jkheit

    Oh, I've reset it (and rebooted in safe mode to enable that apps) more than twice, and I think even more than ten times, so this doesn't help in my case.

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 21, 2014 11:33 AM in response to Toby DeVoss
    Level 9 (73,336 points)
    Applications
    Nov 21, 2014 11:33 AM in response to Toby DeVoss

    Hi,

     

    You are welcome.

     

     

    3Sigcopy2.png

    7:32 PM      Friday; November 21, 2014

     

      iMac 2.5Ghz i5 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 Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 21, 2014 11:34 AM in response to kadavr
    Level 9 (73,336 points)
    Applications
    Nov 21, 2014 11:34 AM in response to kadavr

    HI,

     

    Access ~/Library/Preferences whilst Messages is Quit.

    Find the com.apple.ichat.plist

    Drag this to the Trash

    Restart the app.

     

     

    3Sigcopy2.png

    7:34 PM      Friday; November 21, 2014

     

      iMac 2.5Ghz i5 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 Austin EdTech,

    Austin EdTech Austin EdTech Nov 24, 2014 10:01 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 24, 2014 10:01 AM in response to Linc Davis

    Any help with this would be very appreciated.  (I am a late adopter on purpose and hopefully there is an answer to this by now.)

     

    MBP 2010 just updated to Yosemite.  iMessage worked on all networks prior to update.  Other devices still work, but MBP does not. 

     

    When sending an iMessage, the blue progress bar stops about a half inch from completion.  Eventually, I get the Failed to send icon.

    I flahsed PRAM, tried in Safe Mode.  Logged out and back in several times.

     

    From Console:

    11/24/14 11:47:37.529 AM Messages[966]: [Warning] Calling imageDataBlocking from thread other than main thread.

    11/24/14 11:47:43.328 AM com.apple.xpc.launchd[1]: (com.apple.imtransferservices.IMTransferAgent) The _DirtyJetsamPriority key is not available on this platform.

    11/24/14 11:47:43.328 AM com.apple.xpc.launchd[1]: (com.apple.imtransferservices.IMTransferAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

    11/24/14 11:47:43.328 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

    11/24/14 11:47:43.354 AM icbaccountsd[977]: Connection error while checking Apple Internalness. Error: Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection to service named com.apple.CrashReporterSupportHelper was invalidated.) UserInfo=0x7fd83b101670 {NSDebugDescription=The connection to service named com.apple.CrashReporterSupportHelper was invalidated.}

    11/24/14 11:50:22.220 AM mdworker[995]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"

    11/24/14 11:52:31.727 AM identityservicesd[639]: [Warning] FTMessageDelivery failed! Error (APSErrorDomain:4): Timeout connecting to server (null)

     

    That help?

    HMartin

  • by Toby DeVoss,

    Toby DeVoss Toby DeVoss Nov 24, 2014 11:13 AM in response to Austin EdTech
    Level 1 (5 points)
    Mac OS X
    Nov 24, 2014 11:13 AM in response to Austin EdTech

    As you can tell ....you are not alone! However, with Ralph Johns' brilliant assistance I finally got mine working.

     

    Check your font handling application for AppleGothic. On my machine there is an AppleGothic locked on as part of the system .....however, a little further on in the list there is yet another AppleGothic. When I activated it ...voila!

     

    Good luck!

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 24, 2014 12:53 PM in response to Austin EdTech
    Level 9 (73,336 points)
    Applications
    Nov 24, 2014 12:53 PM in response to Austin EdTech

    Hi,

     

    The com.apple.imtransferservices.IMTransferAgent is a small part of the support applications that help Messages do it's job.

    It is involved with sending Pictures and files over a Buddy List connection (as opposed to an iMessages one).

     

    The com.apple.imfoundation.IMRemoteURLConnectionAgent is related to the use of IMAgent and you should check it is not blocked if you use apps like Little Snitch.

     

    I would reinstall the OS at this point as it looks like it is trying to perform an action and looking for  piece that is no longer there.

     

     

     

     

    3Sigcopy2.png

    8:53 PM      Monday; November 24, 2014

     

      iMac 2.5Ghz i5 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 Austin EdTech,

    Austin EdTech Austin EdTech Nov 24, 2014 1:02 PM in response to Ralph Johns (UK)
    Level 1 (0 points)
    Nov 24, 2014 1:02 PM in response to Ralph Johns (UK)

    By "could be blocked" , is there something in the OS that would do that?  The problem didn't exist before the update and now exists on all network connections. 

     

    When I login, all of my iOS devices pop up with the "apple ID user is now using Apple Facetime/iMessage etc".  So, I know it is communicating with a server. Would more code help direct me a little further down the road?  (I didn't want to drop 1000 lines of code on anyone.)

     

    hm

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 24, 2014 1:46 PM in response to Austin EdTech
    Level 9 (73,336 points)
    Applications
    Nov 24, 2014 1:46 PM in response to Austin EdTech

    Hi,

     

    I use an app called Little Snitch.

    It will tells me and ask me in most cases (as I have it set that way) for both incoming and outgoing connections.

    It will tell me the Server and the port that is about to be used.

     

    It is set to be allowed without asking me in my Little Snitch settings

    Screen Shot 2014-11-24 at 21.16.14.png

    You can see that on the right t lists many Apple IP addresses to make sure it can get through.

    They will all answer as Apple.com

     

    Sometimes if the System Preferences > Network > Advanced Button > DNS tab does not list the ISP's DNS server (only the router as in 192.168.x.x) then it can be an issue.

    However the System is not likely to be specifically blocking this.

     

    I think what is more likely is that the Upgrade has ended up with mixed bits.

    That is to say the as well as the main Messages app there is IMAgent and the items associated with it in System/Library/PrivateFrameworks/IMfoundation.framework  and well as items in IMCore.framework

     

    When there is an Upgrade or an Update to the OS that includes a Messages update then it is likely that these behind the scenes bits also get updated.

    It is important that they "match".

     

    With iChat 1 though Messages 8 in Mavericks it has been clear where the updates have been as the apps have ended up with sub numbers at changes.

    (as in Leopard and iChat 4.0.9 by the time you get to OS X 10.5.8)

    It was less clear in Mavericks  which remained at "Messages 8" despite three known Build changes.

    Yosemite calls the app also "Messages 8" despite some radical changes to the Mavericks version.

     

    The frameworks items above can be opened, but they can also be right clicked and show the Get Info panel as they are in fact a package.

    My IMCore is at version 10 and created on September 27th 2014

    However this can be  lengthy task as there are now several linked frameworks items in PrivateFrameworks  as well as some in just System/Library/Frameworks.

     

    There is a chance that running Repair Permissions for Disk Utility  (Applications/Utilities) on the Mac may join things up properly but I do feel it is a bit deeper than that.

     

     

     

     

    3Sigcopy2.png

    9:45 PM      Monday; November 24, 2014

     

      iMac 2.5Ghz i5 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 kadavr,

    kadavr kadavr Nov 24, 2014 4:50 PM in response to Ralph Johns (UK)
    Level 1 (0 points)
    Nov 24, 2014 4:50 PM in response to Ralph Johns (UK)

    Thanks Ralph, really tried that before, still no luck. By the way, on my wife's pro 13" there is currently the same problem, though she is still on Mavericks. We tried different network connections as well.

     

    =\

  • by Ralph Johns (UK),

    Ralph Johns (UK) Ralph Johns (UK) Nov 25, 2014 12:01 PM in response to kadavr
    Level 9 (73,336 points)
    Applications
    Nov 25, 2014 12:01 PM in response to kadavr

    Hi kadavr,

     

    This thread is now showing as 6 pages long to me.

    Your replies are spaced out with other people joining the thread and I have lost a sense of what we have tried and what we have not in your case.

     

    Would you be so kind as to restate the issue AND what you have tried to do to fix it in as much detail as you can.

    3Sigcopy2.png

    8:01 PM      Tuesday; November 25, 2014

     

      iMac 2.5Ghz i5 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 Skeptic,

    The Skeptic The Skeptic Dec 9, 2014 11:53 AM in response to jkheit
    Level 1 (0 points)
    Dec 9, 2014 11:53 AM in response to jkheit

    I'm having the same issue on my late-2007 MacBook Pro running Yosemite. It seems to have started with the last update, as it was working up until a couple of weeks ago. I'm able to access FaceTime and Messages on my iPhone 4 (iOS 7), my iPad 4 (iOS 8), and my mid-2010 Mac mini server (also running Yosemite).

     

    On the MBP, i've tried wiping the PRAM, resetting the System Management Controller, booting in safe mode, logging in as a guest, turning on Location Services and Automatic Time Zone settings... nothing works.

     

    Now, i should add that i got this MacBook Pro directly from Apple as a replacement for a defective machine. It has NEVER shown the serial number in the "About This Mac" screen or System Profile. I assumed that was because it was an early Intel-based machine. Is the lack of a burned-in serial number on the main logic board the consistent factor with all of these FaceTime and Messages issues?

     

     

    - darren.

first Previous Page 6 of 8 last Next