Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

5 points

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:

--MacVidCard 802.11ac and bluetooth 4.0 upgrade card (http://www.macvidcards.com/store/p33...port_Card.html)
--VisionTek 7750 Eyefinity 6 2GB card (https://www.visiontek.com/graphics-c...rd-detail.html)
--OWC Mercury Accelsior E2 SSD (http://eshop.macsales.com/shop/SSD/P...Accelsior/RAID)
--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/)
--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:

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.
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.
Went through the stuff here to no avail:
messages "An error occurred while activating. Try again later"
My serial number does show in about this Mac.
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.
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.
I have confirmed that others that have done the MacVidCard 802.11ac/bluetooth upgrade are not experiencing this issue.
Same with the USB card.
Since I installed a fresh OS on an external drive, I doubt the OWC Accelsior has anything to do with this.
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).
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:13 PM

118 replies

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.

Dec 9, 2014 12:09 PM in response to The Skeptic

Oh, i should add as well that i have also repaired permissions and done a full verify/repair of the startup drive. Still no luck.

Dec 10, 2014 12:42 PM in response to The Skeptic

Hi,

Since OS X 10.8.2 update the Serial number has been needed.

8:42 pm Wednesday; December 10, 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

Dec 10, 2014 1:26 PM in response to Ralph-Johns-UK

Thanks, Ralph

Is this the official story from Apple Engineering? I spent a couple of hours on the phone yesterday with Level 1 and Level 2 support, and they weren't aware of the issue (or solution). My case has been escalated to Engineering for review.

If this is indeed the case, can i take my MacBook Pro in to an Apple Store and have them burn the serial number to the logic board?

Dec 10, 2014 1:48 PM in response to The Skeptic

Hi,

It has been common since it was discovered soon after OS X 10.8.2 came out.

Many people have posted that they had their Serial Number flash to the board at their Local Apple Store (I have yet to see someone Post that an Apple Authorise Service Provider has done it).

I find that people often report Level 1 people don't know stuff.

Level 2 people can depend on their interests in certain apps and also if they have come across things.

9:48 pm Wednesday; December 10, 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

Dec 10, 2014 7:09 PM in response to Ralph-Johns-UK

Well, i had another conversation with my Level 2 support person today, and she confirmed that my main logic board not having a serial number is indeed the issue. I have an appointment at the local Apple Store tomorrow morning to have the serial number burned to the board. Thanks for your insights, Ralph! Much appreciated.

- darren.

Dec 11, 2014 10:41 AM in response to The Skeptic

In and out of the Apple Store in about 15 minutes. Main logic board is now serialized, and all iCloud services are back up and running!

They're running a really cool setup in there now. No more booting up off hard drives. They plug in an Ethernet cable and netboot into a system with all of their diagnostic tools and utilities. In fact, the screen that came up before allowing the tech to do anything else was, "THIS COMPUTER DOES NOT HAVE A SERIAL NUMBER!" 😉

Weird that they've started authenticating against the hardware, but not entirely surprising. I'm amazed they didn't start doing this years ago.

Dec 11, 2014 12:01 PM in response to The Skeptic

No Problem.

8:01 pm Thursday; December 11, 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

Dec 11, 2014 12:05 PM in response to The Skeptic

Hehehehe.

Mountain Lion was years ago 😁

But I do know what you mean.

Strange that when I clicked the email for the other post I could not see this one (hence the "no problem" answer with no other comment.)

8:05 pm Thursday; December 11, 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

neguz

Level 1

0 points

Dec 29, 2014 8:05 AM in response to irviner

Use FontNuke 1.2.4. It helps me.

Dec 29, 2014 6:30 PM in response to jkheit

I have not yet gone through this whole thread (I will) but has anyone seen this yet?

I'm getting "Delivered" notifications from my Late 2009 iMac running Yosemite, but the messages are not getting to the intended recipients.

Thanks.

12/29/14 6:24:10.886 PM identityservicesd[362]: ApplePushService: <APSConnection: 0x7fdb38724c80> Received message from apsd: <APSIncomingMessage: 0x7fdb3860e590> but it didn't match the enabled topics: (

) or opportunistic topics: (

)

12/29/14 6:24:11.904 PM identityservicesd[362]: ApplePushService: <APSConnection: 0x7fdb38724c80> Received message from apsd: <APSIncomingMessage: 0x7fdb38666f50> but it didn't match the enabled topics: (

) or opportunistic topics: (

)

12/29/14 6:24:11.904 PM identityservicesd[362]: ApplePushService: <APSConnection: 0x7fdb38724c80> Received message from apsd: <APSIncomingMessage: 0x7fdb38667790> but it didn't match the enabled topics: (

) or opportunistic topics: (

)

12/29/14 6:24:11.905 PM identityservicesd[362]: ApplePushService: <APSConnection: 0x7fdb38724c80> Received message from apsd: <APSIncomingMessage: 0x7fdb3854f130> but it didn't match the enabled topics: (

) or opportunistic topics: (

)

Dec 29, 2014 7:27 PM in response to jkheit

More errors. Now I've gotten it to at least tell me that the message was NOT delivered, so I see that as a plus.

12/29/14 7:25:08.476 PM identityservicesd[337]: [Warning] Warning, missing tel:+14xxxxxxxx3 in (null)

12/29/14 7:25:08.476 PM identityservicesd[337]: [Warning] Warning, missing mailto:xxxxxx@icloud.com in (null)

12/29/14 7:25:09.599 PM com.apple.xpc.launchd[1]: (com.apple.imdmessageservices.IMDMessageServicesAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

12/29/14 7:25:09.599 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

12/29/14 7:25:18.053 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

alcheme

Level 1

116 points

Dec 30, 2014 9:27 AM in response to jkheit

Resetting the P RAM did not work for me.

eplpw

Level 1

0 points

Jan 7, 2015 2:54 AM in response to jkheit

This worked for me, too! Cheers!

MBA mid-2011 using OS 10.10.1

arjay67

Level 1

14 points

Jan 22, 2015 2:51 PM in response to jkheit

{bump}

For those who have been in contact with Apple Support and been given the, "This issue has been referred to Engineering" has anyone heard anything more regarding the status? I attempted to contact them by email two weeks ago and they will no longer respond.

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