Fix “Your Mac was unable to communicate with your Apple Watch” Error
Some Mac users may experience an issue when unlocking their Mac with Apple Watch where they discover it is no longer working as expected, despite all the conditions being met to do so. Instead, users may get an error message that says “Your Mac was unable to communicate with your Apple Watch. Make sure your Apple Watch is unlocked and on your wrist, and your iPhone is unlocked” despite those conditions being met.
If you encounter this error, below we’ll run through some troubleshooting methods to fix the issue and get Apple Watch to unlock the Mac again as expected.
Resolving the “Your Mac was unable to communicate with your Apple Watch” Error
Here are four troubleshooting steps to fix problems with the Apple Watch unlocking the Mac.
1: Double-check & Toggle Mac Settings
First, make sure you have already gone to System Settings / Preferences > Security & Privacy > General > and made sure “Use your Apple Watch to unlock apps and your Mac” is checked and enabled.
If the setting is already enabled, try toggling the setting for “Use your Apple Watch to unlock your Mac” off, wait a few moments, and then turn it back on again.
You can always run through the tutorial for setting up Mac unlocking via Apple Watch if needed.
2: Ensure Apple Watch is on properly, and unlocked
Next, make sure your Apple Watch is unlocked on your wrist as is typically required, as is your iPhone.
If the Apple Watch is not properly seated on your wrist, the unlock feature typically will not work.
3: Reboot the Mac & Apple Watch
Rebooting the Mac and Apple Watch also may resolve the issue, particularly if you just toggled the feature off and on again on the Mac side of things.
4: Mac still not unlocking with Apple Watch? Trash the Keychain Entries & Preferences, Re-Enable
If the problem still persists, the solution detailed below may work to resolve the “unable to communicate with Apple Watch” error on Mac. Be sure to backup the Mac before beginning this process, because you may corrupt the keychain if something goes awry, which would prevent you from having access to the keychain data (saved passwords, etc).
- Backup the Mac before proceeding
- Open “Keychain Access” via Spotlight by hitting Command+Spacebar and typing “Keychain Access” and hitting return
- From the “View” menu choose “Show Invisible Items”
- Next, search for “Auto Unlock”
- Select all entries for “Auto Unlock” and delete them
- Now search for “AutoUnlock” and select and delete all of those entries for tlk, tlk-nonsync, classA, classC
- Quit out of Keychain Access
- Now from the Finder, hit Command+Shift+G to bring up Go To Folder and enter the following path or manually navigate there via your home directory:
- Trash the files “ltk.plist” and “pairing-records.plist”
- Restart the Mac
- Go to the Apple menu, select ‘System Preferences’ and go to “Security & Privacy” and to the General tab
- Check the box to enable “Use your Apple Watch to unlock apps and your Mac”, it may need to be enabled twice if the first attempt fails to enable the feature
- Try unlocking the Mac with the Apple Watch again, it should work
This particular troubleshooting procedure was submitted to us from Chris (thanks!) and it comes from the Apple discussion support forums. This seems to do the trick to resolve the problem for most users who are experiencing the “Your Mac was unable to communicate with your Apple Watch” error continuously, whether out of the blue, after updating a Mac or Apple Watch, or after using Migration Assistant.
5: Using Ethernet on the Mac? Unplug Ethernet Connection Temporarily
Several users in our comments have discovered that if they’re using a wired ethernet connection on the Mac, they will see this error message with the Apple Watch, regardless of whether or not the Mac is also using wi-fi. In this situation, try disconnecting the Ethernet cable connection, then toggling the setting for “Use your Apple Watch to unlock apps and your Mac” again. Once it works and is enabled, you can reconnect the wired ethernet connection again.
Did the above troubleshooting solutions work for you? Did you find another solution? Let us know your experiences in the comments.