Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
hamzab

iMessage not working - iCloud/Internet etc working - Changed boot.plist file and network.plist file - Help

420 posts in this topic

Recommended Posts

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.apple.com/identity/validation/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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

 

 

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

If this help, this my hac log

 

 

2012-12-30 19:46:03 +0200 Messages[28454]: [Warning] Empty account query with service: iMessage

2012-12-30 19:46:03 +0200 com.apple.SecurityServer[15]: Session 100068 created

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] *** Listener ID: com.apple.mail does not have capability: (Status), not allowing request

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 1 IMFoundation 0x00007fff82fdcbe2 IMLogBacktraceToDepth + 69

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 2 imagent 0x000000010c94ade8 imagent + 81384

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 3 imagent 0x000000010c94bf6a imagent + 85866

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 4 CoreFoundation 0x00007fff8dcc463c __invoking___ + 140

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 5 CoreFoundation 0x00007fff8dcc44d7 -[NSInvocation invoke] + 263

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 6 CoreFoundation 0x00007fff8dcc46a9 -[NSInvocation invokeWithTarget:] + 57

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 7 IMFoundation 0x00007fff82fd95d5 im_local_object_peer_event_handler + 7128

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 8 IMFoundation 0x00007fff82fd96b3 im_local_object_peer_event_handler + 7350

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 9 IMFoundation 0x00007fff82fd9767 im_local_object_peer_event_handler + 7530

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 10 Foundation 0x00007fff8ed40677 __NSThreadPerformPerform + 225

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 11 CoreFoundation 0x00007fff8dc50101 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 12 CoreFoundation 0x00007fff8dc4faed __CFRunLoopDoSources0 + 445

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 13 CoreFoundation 0x00007fff8dc72dc5 __CFRunLoopRun + 789

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 14 CoreFoundation 0x00007fff8dc726b2 CFRunLoopRunSpecific + 290

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 15 Foundation 0x00007fff8ed4889e -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 16 Foundation 0x00007fff8ece118a -[NSRunLoop(NSRunLoop) run] + 74

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 17 imagent 0x000000010c93f0ab imagent + 32939

2012-12-30 19:46:20 +0200 imagent[197]: [Warning] 18 libdyld.dylib 0x00007fff854fb7e1 start + 0

Share this post


Link to post
Share on other sites

 

 

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.

 

I took this approach, too. But bad news is that I found no evidence that Mac had the same log entries as hackintosh's. I'm wondering how apple distinguish a Mac and hackintosh. If we know it, we might crack it.

Share this post


Link to post
Share on other sites

As I mentioned before, it's failing when trying to get a valid token from apple server and the handshake process is detailed here http://imfreedom.org/wiki/IMessage which also has directions to enable advanced debugging for applepushserviced which appears to be where the failure is. There are 3 seperate process involved in making the connection/validation: iChat, IMAgent and applepushserviced. Using a network monitor (i.e. Hands Off!) you can see what connections each process makes and data sent/recieved. Doing the same on a real Mac for comparison would be super helpful! There is also a link for github project with tools for debugging and setting up a push proxy (but this is more work around than actual fix) I need to finish fine tuning new HD7970 and watch Football before I can look into it too much more, and only real mac I have won't run ML. Last week before leaving for holiday quickly copied network info from IMagent but not the push service as I should have done, but here is what I'm talking about:

Connection history for IMRemoteURLConnectionAgent (/System/Library/PrivateFrameworks/IMFoundation.framework/XPCServices/IMRemoteURLConnectionAgent.xpc/Contents/MacOS/IMRemoteURLConnectionAgent)Total sent: 56.30kB Total received: 85.69kB service2.ess.apple.com (17.154.239.37) on port 443 (https) using protocol 6 (TCP), sent: 22.01kB and received: 12.63kBstatic.ess.apple.com (216.156.147.11) on port 80 (http) using protocol 6 (TCP), sent: 448B and received: 14.46kB service2.ess.apple.com (17.173.255.73) on port 443 (https) using protocol 6 (TCP), sent: 22.02kB and received: 12.62kB static.ess.apple.com (140.174.24.81) on port 80 (http) using protocol 6 (TCP), sent: 448B and received: 14.46kB service.ess.apple.com (17.173.255.51) on port 443 (https) using protocol 6 (TCP), sent: 5.20kB and received: 6.60kB init.ess.apple.com (216.156.147.57) on port 80 (http) using protocol 6 (TCP), sent: 112B and received: 4.23kB service.ess.apple.com (17.173.255.24) on port 443 (https) using protocol 6 (TCP), sent: 5.75kB and received: 7.99kB init.ess.apple.com (140.174.24.32) on port 80 (http) using protocol 6 (TCP), sent: 224B and received: 8.46kB init.ess.apple.com (140.174.24.25) on port 80 (http) using protocol 6 (TCP), sent: 112B and received: 4.23kB

I would expect only the https connections to be involved in authentication. Need to see exactly which server connection is the failure point and if it's the sent or received response that triggers it, you can then look on the web page I linked and see in the examples what info is sent to, or received from that server during that step of the handshake. Again same info from real mac needed too. Then we can have it narrowed down to the actual cause and stop making wild ass guesses but instead actually start working toward a solution!

 

P.S: I think it's fair to say that without further debugging enabled, the same console logs being posted everywhere are useless.

Share this post


Link to post
Share on other sites

 

 

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.

 

That's a good news! But I'm wondering why all hackintoshs are down but not so many macs.

Share this post


Link to post
Share on other sites

That's a good news! But I'm wondering why all hackintoshs are down but not so many macs.

I once made a guess. Due to heavy load on Apple imessage server, Apple has to restrict the usage of Message. They may change the rules they used to accept the verification. Anyway, just personal opinion :D

Share this post


Link to post
Share on other sites

I once made a guess. Due to heavy load on Apple imessage server, Apple has to restrict the usage of Message. They may change the rules they used to accept the verification. Anyway, just personal opinion :D

You make a good point, it is a free service after all so I would understand them not wanting to upgrade so Hack's can use it and may be same reason Lion beta was discontinued. Similar to how unsupported devices were overloading the Siri servers, otherwise they probably wouldn't have made such effort to block it. iMessage was getting slow to send and receive at times, same as how Siri timeouts would occur when Spire came out.

Share this post


Link to post
Share on other sites

This issue also affects virtualized OS X systems, and those are a supported configuration by Apple, so I am inclined to believe that this is not intentional.

 

There seem to be some commonality with tokenized logins for other services, and authenticating those as well. Case in point, I changed the password on my iCloud account that I use with iMessage, since I wanted to force my tokens to refresh on my devices. Long story short, I can't login to iCloud.com web services with my new password, nor can I use iMessage on my Hacs. I'll see if my phone and iPads are punted as expected but if they don't let me re-authenticate either I believe this is an accident or symptomatic of a larger issue.

Share this post


Link to post
Share on other sites

an addition worthy of not editting my previous post:

 

 

$ curl --data-ascii @f  https://service.ess.apple.com/WebObjects/VCProfileService.woa/wa/authenticateUser  
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
 <key>message</key><string>status = 5012, INVALID NAME OR PASSWORD</string>
 <key>status</key><integer>5012</integer>
</dict>
</plist>

 

Presently this is the result I'm getting from the imessage auth service, where @f is of course the file containing my plist with my authentication bits. If someone else that knows about the iMessage auth service and associated bits, please let me know if you're getting the same message without a recent password change and we'll see if something is happening with the iMessage auth service in general, or if this is because I changed my password and it hasn't propogated to that service yet (which doesn't make sense seeing as how I think they're using kerb anyway).

 

Here's an example you can use for what you should be POSTing to that url.

 

 


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
      <key>password</key>
      <string>lkjasdkfjlk;ajsdf;ljasdfj</string>
      <key>username</key>
      <string>myappleid@me.com</string>
</dict>
</plist>

Share this post


Link to post
Share on other sites

It will contain an auth token in the plist, and you use that token when you generate a PEM-encoded CSR to send back to the service. This isn't going to fix your iMessage in one step, I'm trying to see where it is failing.

 

When iMessage talks to various web services it prepends some headers to the POST like:

 

 

x-ds-client-id: t:(hexadecimal string to identify software or computer/device)
x-protocol-version: 4
x-vc-profile-id: D:(the profile-id)
x-vc-auth-token: (the auth token)

 

So, for whatever reason, it seems likely that the ds-client-id that is generated by your virtual machine or Hac is probably failing, and it isn't widely known what the method used for generating that is. Or, some people have mentioned they have logs showing a failure here when it is successful in logging in.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×