406 replies to this topic

[fau7i]

Oh no... I hope it isn't true

Although I don't really use this app for chatting, I find iMessage as a fast way to share camera shots between Apple devices.

[PookyMacMan]

p.H, on 23 December 2012 - 12:43 AM, said:

Sorry for that. But your test just re-testifies that Apple is restricting hackintosh usage from some perspectives.

I have to firmly disagree. Apple is not conspiring against hackintosh. It really wouldn't work anyway. Besides...

eep357, on 21 December 2012 - 04:49 AM, said:

Yes many real macs have same problem and for a variety of reasons, but in comparison to how many real macs don't have this problem it's a small number, so if your real mac is fine and hack is not, don't expect that to automatically mean it only effects hacks, it's just that you weren't lucky enough to win the lottery.

[p.H]

PookyMacMan, on 23 December 2012 - 07:04 PM, said:

I have to firmly disagree. Apple is not conspiring against hackintosh. It really wouldn't work anyway. Besides...

Maybe Apple thought it's the hackintosh that caused its message server down

[HELLFISH]

Well shoot, today my iMessage stopped working as well.  All was fine up until this morning, now I can not login.  Seems Apple is indeed cracking down on hacks.

[ccsr]

I just logged in on my image again, iMessage is working great. No issues at all. I wouldn't dare logout though. Tried to copy all the certificates and iMessage related encryption and login and it copied fine, because I'm not logged on it doesn't work. One thing to note is that all my certificates are expiring late 2013, earliest September 2013.

I'm out of ideas. It would be nice if we could sort this out a.s.a.p.

I quite miss it, although I've got an iPhone 4S and an iPad. It's a handy feature to have, shame if we lost it. We need to find out how Apple is authenticating the login and what else has changed since the 18th/19th of this month.

[p.H]

You managed to log in imessage in your hack ?

[ccsr]

No, It's already logged in. That's the problem. I haven't logged out. As long as you are logged on you won't be kicked out.
At least that's the way I understand it. I have a Superduper image, last backed up to it a week or two ago. If i start that image up iMessage is logged on and I tested sending messages to my iPhone and iPad and it works fine.

[p.H]

You're right. I used to be logged on several days ago and was able to send messages. But having seen people complaining about this issue, I decided to give it a shot myself. So I was not able to sign in again. hhahaha

[mrengles]

Just checking in to get some email notifications on the progress of this thread.

Same here iMessages stopped working a couple days ago.

This was Apples way of saying Merry Christmas Hackintosh Users!

[lisai9093]

I've found something strange in the console when I tried to log in to iMessage:

12/27/12 1:51:47.070 PM Messages[1513]: [Warning] Empty account query with service: iMessage
12/27/12 1:51:47.402 PM com.apple.SecurityServer[15]: Session 100052 created

It appears that some information required is not present. Here is what looks like in a real Mac, when encountering an error:

9/19/12 11:59:28.787 PM com.apple.SecurityServer[17]: Session 100014 created
9/19/12 11:59:32.216 PM Messages[256]: [Warning] Empty account query with service: iMessage
9/19/12 11:59:32.598 PM imagent[163]: [Warning] TRUST validation failed with result 5
9/19/12 11:59:32.598 PM imagent[163]: [Warning] FTFaceTimeServerBag: URL bag data invalid (not valid)
9/19/12 11:59:57.057 PM Console[269]: Marker - Sep 19, 2012 11:59:57 PM

See the different? The Apple server does not even bother to send a validation failure message to my computer. I guess this could be a clue and wonder what you guys have in your console app?

[ccsr]

This looks like it's the way forward. Why did the real Mac got a failed validation?

[eep357]

Still out of town for another day or so, but looks like it's similar to iphone method and uses push services. May be possible to make it work in similar to methods used for siri on unsupported devices. Some more info here http://imfreedom.org/wiki/IMessage and here https://github.com/meeee/pushproxy which basically involves extracting valid keys/certs from keychain and side stepping the push server via proxy. Doesn't look fun, but there may be some hope, at least to keep logged in account from revalidating and staying logged in if you can get that far.

[rcork]

I too have fallen victim to this issue. Sometime in the last week i was signed out of Messages. I think it happened right after i activated a new iPad mini and setup Messages and Facetime on the iPad. Now i can't log back in. I have tried installing a fresh version of Mountain Lion on another drive but that didn't work. Hopefully someone can figure out what is going on here.

[afd_sg]

This is likely not only a hackintosh issue as it also effects jailbroken iPhones.  To combat the jailbreaking they have implemented a fix to prevent people copy PUSH certificates from a working unmodded iPhone to a jailbroken one.

I am of the opinion that this entry in my log shows what the problem is on the hackintosh. I can also confirm that if I move the disk to a real mac pro and boot it, iMessage works fine, put it back in the hack and it doesn't.

This is the interesting entry that I think may be responsible.


29/12/12 11:45:13.587 AM imagent[222]: [Warning] Missing push token
29/12/12 11:45:15.591 AM imagent[222]: [Warning] FTMessageDelivery failed! (HTTP Status Code: 0) Error (NSURLErrorDomain:-1003): A server with the specified hostname could not be found. http://static.ess.ap.../cert-1.0.plist
29/12/12 11:45:16.612 AM com.apple.launchd[1]: (com.apple.coreservices.appleid.authentication[183]) Exit timeout elapsed (20 seconds). Killing

Question is how do we obtain this required TOKEN on a hack?

[lisai9093]

ccsr, on 27 December 2012 - 07:01 PM, said:

This looks like it's the way forward. Why did the real Mac got a failed validation?

I think it is something to do with the hosts file. Although it is different problem with hackintosh, it might be worthy to look at.

[rcork]

lisai9093, on 29 December 2012 - 06:34 PM, said:

I think it is something to do with the hosts file. Although it is different problem with hackintosh, it might be worthy to look at.

I don't believe it has anything to do with host files. Some people suggested that incorrect entries in the host file prevented imagent from communicating with Apple's servers but i have a clean host file and this issue still persists. If it helps anyone, here is the log when i try to enable iMessage:

12/29/12 3:53:51.713 PM imagent[237]: [Warning] Empty account query with service: iMessage
12/29/12 3:53:51.764 PM com.apple.SecurityServer[18]: Session 100126 created
12/29/12 3:54:03.875 PM imagent[237]: [Warning] *** Listener ID: com.apple.mail  does not have capability: (Status), not allowing request
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 1   IMFoundation						0x00007fff91b5abe2 IMLogBacktraceToDepth + 69
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 2   imagent							 0x0000000105b60de8 imagent + 81384
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 3   imagent							 0x0000000105b61f6a imagent + 85866
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 4   CoreFoundation					  0x00007fff8ac4025c __invoking___ + 140
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 5   CoreFoundation					  0x00007fff8ac400f7 -[NSInvocation invoke] + 263
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 6   CoreFoundation					  0x00007fff8ac402c9 -[NSInvocation invokeWithTarget:] + 57
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 7   IMFoundation						0x00007fff91b575d5 im_local_object_peer_event_handler + 7128
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 8   IMFoundation						0x00007fff91b576b3 im_local_object_peer_event_handler + 7350
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 9   IMFoundation						0x00007fff91b57767 im_local_object_peer_event_handler + 7530
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 10  Foundation						  0x00007fff92a5bd3a __NSThreadPerformPerform + 225
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 11  CoreFoundation					  0x00007fff8abcbd21 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 12  CoreFoundation					  0x00007fff8abcb70d __CFRunLoopDoSources0 + 445
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 13  CoreFoundation					  0x00007fff8abee9e5 __CFRunLoopRun + 789
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 14  CoreFoundation					  0x00007fff8abee2d2 CFRunLoopRunSpecific + 290
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 15  Foundation						  0x00007fff92a63f5e -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 16  Foundation						  0x00007fff929fc75a -[NSRunLoop(NSRunLoop) run] + 74
12/29/12 3:54:03.877 PM imagent[237]: [Warning] 17  imagent							 0x0000000105b550ab imagent + 32939
12/29/12 3:54:03.877 PM imagent[237]: [Warning] 18  libdyld.dylib					   0x00007fff9297a7e1 start + 0

[C.44]

It seems to be a widespread problem existing mainly on Hackintoshes. I recently added an iCloud email addy to my AppleID and ever since i've been logged / locked out as well. I just hope that somehow this is an oversight on Apple's end and not an actual countermeasure, if that'd be the case i'm extremely worried about facetime (less but still), itunes, the appstore and all of my purchased applications.

[p.H]

rcork, on 29 December 2012 - 10:56 PM, said:

I don't believe it has anything to do with host files. Some people suggested that incorrect entries in the host file prevented imagent from communicating with Apple's servers but i have a clean host file and this issue still persists. If it helps anyone, here is the log when i try to enable iMessage:

12/29/12 3:53:51.713 PM imagent[237]: [Warning] Empty account query with service: iMessage
12/29/12 3:53:51.764 PM com.apple.SecurityServer[18]: Session 100126 created
12/29/12 3:54:03.875 PM imagent[237]: [Warning] *** Listener ID: com.apple.mail does not have capability: (Status), not allowing request
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 1 IMFoundation					 0x00007fff91b5abe2 IMLogBacktraceToDepth + 69
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 2 imagent							 0x0000000105b60de8 imagent + 81384
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 3 imagent							 0x0000000105b61f6a imagent + 85866
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 4 CoreFoundation					 0x00007fff8ac4025c __invoking___ + 140
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 5 CoreFoundation					 0x00007fff8ac400f7 -[NSInvocation invoke] + 263
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 6 CoreFoundation					 0x00007fff8ac402c9 -[NSInvocation invokeWithTarget:] + 57
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 7 IMFoundation					 0x00007fff91b575d5 im_local_object_peer_event_handler + 7128
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 8 IMFoundation					 0x00007fff91b576b3 im_local_object_peer_event_handler + 7350
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 9 IMFoundation					 0x00007fff91b57767 im_local_object_peer_event_handler + 7530
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 10 Foundation						 0x00007fff92a5bd3a __NSThreadPerformPerform + 225
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 11 CoreFoundation					 0x00007fff8abcbd21 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 12 CoreFoundation					 0x00007fff8abcb70d __CFRunLoopDoSources0 + 445
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 13 CoreFoundation					 0x00007fff8abee9e5 __CFRunLoopRun + 789
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 14 CoreFoundation					 0x00007fff8abee2d2 CFRunLoopRunSpecific + 290
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 15 Foundation						 0x00007fff92a63f5e -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 16 Foundation						 0x00007fff929fc75a -[NSRunLoop(NSRunLoop) run] + 74
12/29/12 3:54:03.877 PM imagent[237]: [Warning] 17 imagent							 0x0000000105b550ab imagent + 32939
12/29/12 3:54:03.877 PM imagent[237]: [Warning] 18 libdyld.dylib					 0x00007fff9297a7e1 start + 0

Couldn't agree with you more.

[lisai9093]

rcork, on 29 December 2012 - 10:56 PM, said:

I don't believe it has anything to do with host files. Some people suggested that incorrect entries in the host file prevented imagent from communicating with Apple's servers but i have a clean host file and this issue still persists. If it helps anyone, here is the log when i try to enable iMessage:

12/29/12 3:53:51.713 PM imagent[237]: [Warning] Empty account query with service: iMessage
12/29/12 3:53:51.764 PM com.apple.SecurityServer[18]: Session 100126 created
12/29/12 3:54:03.875 PM imagent[237]: [Warning] *** Listener ID: com.apple.mail  does not have capability: (Status), not allowing request
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 1   IMFoundation						0x00007fff91b5abe2 IMLogBacktraceToDepth + 69
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 2   imagent							 0x0000000105b60de8 imagent + 81384
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 3   imagent							 0x0000000105b61f6a imagent + 85866
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 4   CoreFoundation					  0x00007fff8ac4025c __invoking___ + 140
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 5   CoreFoundation					  0x00007fff8ac400f7 -[NSInvocation invoke] + 263
12/29/12 3:54:03.875 PM imagent[237]: [Warning] 6   CoreFoundation					  0x00007fff8ac402c9 -[NSInvocation invokeWithTarget:] + 57
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 7   IMFoundation						0x00007fff91b575d5 im_local_object_peer_event_handler + 7128
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 8   IMFoundation						0x00007fff91b576b3 im_local_object_peer_event_handler + 7350
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 9   IMFoundation						0x00007fff91b57767 im_local_object_peer_event_handler + 7530
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 10  Foundation						  0x00007fff92a5bd3a __NSThreadPerformPerform + 225
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 11  CoreFoundation					  0x00007fff8abcbd21 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 12  CoreFoundation					  0x00007fff8abcb70d __CFRunLoopDoSources0 + 445
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 13  CoreFoundation					  0x00007fff8abee9e5 __CFRunLoopRun + 789
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 14  CoreFoundation					  0x00007fff8abee2d2 CFRunLoopRunSpecific + 290
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 15  Foundation						  0x00007fff92a63f5e -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
12/29/12 3:54:03.876 PM imagent[237]: [Warning] 16  Foundation						  0x00007fff929fc75a -[NSRunLoop(NSRunLoop) run] + 74
12/29/12 3:54:03.877 PM imagent[237]: [Warning] 17  imagent							 0x0000000105b550ab imagent + 32939
12/29/12 3:54:03.877 PM imagent[237]: [Warning] 18  libdyld.dylib					   0x00007fff9297a7e1 start + 0

Are you using a Mac or hackintosh? I heard some Mac users do have trouble in logging into iMessage and it is because of the hosts file. But for hackintosh it is a different story.

What I am trying to do is to simply compare the log entries shown in Macs and hackintoshs, and hope it gives some clues of what is wrong.

[rcork]

lisai9093, on 30 December 2012 - 08:03 AM, said:

Are you using a Mac or hackintosh? I heard some Mac users do have trouble in logging into iMessage and it is because of the hosts file. But for hackintosh it is a different story.

What I am trying to do is to simply compare the log entries shown in Macs and hackintoshs, and hope it gives some clues of what is wrong.

These log entries are from my hackintosh. However, i was curious if these log entries showed up on my "real" macbook pro and indeed they do. So these errors are not specific to just my hackintosh.