Is it still possible to sign-in to iMessage on Mavericks? I keep getting this everytime I try.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Can't sign-in to iMessage on Mavericks?
- Thread starter TCOS2
- Start date
- Sort by reaction score
Per the official Apple iCloud support requirements https://support.apple.com/en-us/118308, since 2023 at the latest, Mavericks is no longer a minimum. Try installing Legacy Proxy by Wowfunhappy Fixing Mavericks's Outdated HTTPS, and signing back in. It applies to FaceTime as well.
It is my iMessage on Mavericks:
It is my iMessage on Mavericks:
Last edited:
Hi. I've been using the Legacy Proxy by wowfunhappy for a while now, and it's had no impact. I do notice, however, that if I select "Create an Apple ID" within iMessage, I get this.
I don't know if it's related to my problem, I just thought I'd point it out.
You better write in the Legacy Proxy thread or send a PM to Wowfunhappy. I might've not seen this error because I haven't signed out of iMessage.
I love the "Would you like to connect anyway?" message with only one option to select from.
Well that's interesting!
Do any messages appear in console.app immediately before or after this message?
The text would appear to indicate an https problem. But as I have been saying in the other thread, my proxy does not modify iMessage traffic because Apple uses certificate pinning.
@f54da keeps reminding me we could bypass the certificate pinning if we wanted to, maybe this means we should.
But first, please, what appears in Console?
Thanks for your reply! Sorry for my late reply, I've got a very erratic schedule at the moment.
I've attached a log from Console beginning just before I opened the Messages app. All I've done is remove my email and the push token.
Thanks again!
Thanks. Unfortunately this doesn't have the `SSLHandshake failed` I was hoping to see.
On the plus side, it sounds like iMessage has randomly started working again for some people?
Strange, I've been having this problem for months now. Tried on multiple machines and multiple accounts.
Alright, I figured out how to get into iMessage! https://apple.stackexchange.com/q/474584/150839
You can skip steps 6–8 if you don't use iCloud for anything other than Messages.
More details at the link, but the tl;dr is that Messages only gets one sign in attempt per 30 minutes, and two-step verification makes you log in twice in a row.
A general note that while I don't know exactly what is happening, Apple is clearly applying extra scrutiny to sign-ins from Mavericks. Try to avoid doing anything that would make them more suspicious, such as signing in while connected to a VPN.
cc @iPodNano3.
You can skip steps 6–8 if you don't use iCloud for anything other than Messages.
More details at the link, but the tl;dr is that Messages only gets one sign in attempt per 30 minutes, and two-step verification makes you log in twice in a row.
A general note that while I don't know exactly what is happening, Apple is clearly applying extra scrutiny to sign-ins from Mavericks. Try to avoid doing anything that would make them more suspicious, such as signing in while connected to a VPN.
cc @iPodNano3.
Last edited:
It works! Thank you so much for figuring this out! I’ve been looking for a fix for months, and now I have one more reason to stick with OS X Mavericks.
Thank you! This issue has been bothering me for months. I really appreciate it
You're all welcome! By the way, while the method posted works for Messages, at the moment I still can't sign into FaceTime. If you're currently signed in to FaceTime, don't sign out.
thanks! i always knew there would be a way! apple's login process for older devices is very unstable. sometimes it works, sometimes not, and it's so weird to enter the code with my password. i dont really care about facetime, since my mbp camera is trash anyways. tysm!
I will defend this, I actually think it's super clever!
Remember, when Mavericks was released, two-step authentication did not exist for Apple IDs. So apps on Mavericks don't have any sort of third dialog box in their programming where the user can enter an authentication code. Apple found a way to let all of their old clients keep logging in, without compromising the security of the system. Yes it's not the best UX, but once you know the trick it works! (Well except in this case, but that's a separate problem.)
Other companies like Google and Github solve this problem with app-specific passwords/tokens.
Last edited:
100%. I also think adding the 2FA code after your password is a wayyyy better solution than app-specific passwords.
today is a sad day they increased the imessage requirements to 10.12 sierra
but fortunately it still works on mavericks 💀 (i just love that legacy skull emoji)
has anyone been able to get facetime working on mavericks?
wowfunhappy says he was able to use facetime just fine; i think he is just lucky, since i have come across countless posts on the internet saying it worked fine for them until earlier this year when they changed the requirements and it just logged them out.
but fortunately it still works on mavericks 💀 (i just love that legacy skull emoji)
has anyone been able to get facetime working on mavericks?
wowfunhappy says he was able to use facetime just fine; i think he is just lucky, since i have come across countless posts on the internet saying it worked fine for them until earlier this year when they changed the requirements and it just logged them out.
I was at one point, but not for a while, as I said a few posts up:
But iMessage works with this trick.
Last edited:
is it possible to accept the call?
that is about how far i can get in ios 6
i get an alert that someone is calling me, but i cannot accept it; it will say its connecting and then it will just end the call
when i make an outgoing call and they accept, it connects, but the video will freeze after about 5 seconds, and the call will crash
Hmm, I never called an iPhone from my Mac. Calling the Mac from my phone works, but it doesn't the other way around. I signed out and, trying to sign in, got the familiar server error message. Here we are. The day has come. Apple is so nice, decent and forward-thinking: if they don't obsolete their services they won't get revenue.
Amen!
Amen!
Last edited:
As I explained, it wasn't bidirectionally functional. At this point, Apple bastardized it. There wasn't any rationale behind keeping it running.
However, a part of me cries in despair: aren't there ways to deep-hack the Facetime service by identifying the certificate pinning code, injecting the custom one and recompiling the app binary to spoof a valid client? So many smart people out there.
Ok-ok, moving on.
However, a part of me cries in despair: aren't there ways to deep-hack the Facetime service by identifying the certificate pinning code, injecting the custom one and recompiling the app binary to spoof a valid client? So many smart people out there.
Ok-ok, moving on.