How to fix iMessage and FaceTime activation issues on macOS
- apr
- 16
Getting an authentication error trying to log into iMessage or FaceTime? Try this fix!
Apple rightfully has a reputation of having its products "just work". And 99% of the time that adage holds true. Until it doesn't. When things do go wrong, Apple's error messages are cryptic, at times offering no obvious clue as to how to remedy them. One such error is the "Authentication Error" message when trying to log into iMessage and FaceTime on your Mac, even if you've successfully logged into iCloud.
The problem
For a non-obvious reason, my previously properly running Mac could no longer log into iMessage or FaceTime in spite of being successfully logged into iCloud. Notes synced, Documents synced, Photo stream working, continuity functional, etc.
Trying to log into iMessage triggers my two-factor authentication mechanism as expected. But when prompted for my iCloud username and password, and after a long timeout period, I simply get an "Authentication Error".
The potential fix
The fix involves getting Apple's servers to re-initialize your mac hardware to be allowed to access your iCloud services.
Log out of iCloud on the Mac
- Open System Preferences.
- Select iCloud.
- Select Sign Out.
- Select Keep a Copy.
Allow your files to download locally.
- Select Keep on This Mac to keep saved credentials locally.
- Restart you Mac.
Log into your iCloud.com web account
- Open Safari.
- Navigate to iCloud.com.
- Log in to your iCloud account.
- Select Settings.
- Select your problematic Mac.
Click the X to remove the Mac.
- Affirm the deletion.
- Click Done
Log back into iCloud on your Mac
- Open System Preferences.
- Select iCloud.
- Enter your Apple ID.
- Click Next.
- Enter your Mac User Name and Password.
- Select OK.
- Click Next.
Click Allow.
Log into iMessage
- Start iMessage.
- Enter your iCloud credentials.
- Click Next.
- Done!
Final comments
This is but one solution (of the myriad of suggestions found online) that worked for me. Let us know in the comments if this fix helped you too!
