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.
iPhone 13 Users Experiencing 'Unable to Communicate with Apple Watch' Bug With Mask Unlocking
- Thread starter MacRumors
- Start date
- Sort by reaction score
That solved a few issues. I deleted all of the watch in iCloud keychain, then when I went back into unlock in the watch app, the switch was now green.....I also deleted all of the iTunes connections in iCloud Keychain and now it is connecting to my iTunes (Mac Pro 5,1 running Mojave)
I'll give it a shot tomorrow. In some prior update this sort of fix worked (I think.. long ago!).
Going into iCloud Keychain and deleting all items for watch and iTunes solved a few issues. I deleted all of the watch in iCloud keychain, then when I went back into unlock in the watch app, the switch was now green.....I also deleted all of the iTunes connections in iCloud Keychain and now it is connecting to my iTunes (Mac Pro 5,1 running Mojave)
Edit...next day...still many issues.
Edit...next day...still many issues.
Last edited:
I’m fairly certain my watch is now bricked. I tried to do a factory reset to see if that would fix this issue. It got stuck on a reset screen so I reboot the watch. Now it fails to connect or pair.
Brilliant. Thanks, Apple
Brilliant. Thanks, Apple
Apple started moderating my posts on their forums. They didn't like me linking to Reddit or MacRumors. Many reporting identical issue.
I upgraded to iPhone 13 and it initially connected to my Apple Watch (running watchOS8) and now I'm getting the "Unable to Communicate with Apple Watch" error. Anyone else run into this?
Several iPhone 13 users have taken to online forums and social media to report that after receiving their brand new iPhones, they're experiencing a bug preventing it from communicating with their Apple Watch, making what's supposed to be a seamless experience an annoyance.
As outlined on Reddit, after receiving an iPhone 13, some customers cannot toggle on the "Unlock with Apple Watch" feature, allowing users to unlock their iPhones while wearing a mask thanks to their Apple Watch. When attempting to activate the feature, some customers are prompted with an "Unable to communicate with Apple Watch" prompt, with no clear solution.
Posts and comments on Reddit suggest that typical problem-solving solutions aren't working, such as restarting both devices and even unpairing and repairing the Apple Watch to the iPhone. Posts on Twitter and Reddit indicate that the issue is widespread amongst new iPhone 13 users, but at least so far, we aren't seeing reports of other iPhone models being impacted.
The iPhone 13 initially shipped with an outdated build of iOS 15, so customers experiencing the bug should first ensure they're running the latest iOS 15 and watchOS 8 version. Still, even then, reports suggest that does little to amend the issues.
The new bug joins a growing list of bugs related to iOS 15 and the new iPhones, including a bug that may result in Apple Music being inoperative after a restore, a bug that may cause widgets to reset, and a bug impacting reported iPhone and iPad storage.
Apple is currently testing iOS and iPadOS 15.1, but given the growing number of issues experienced by users, the company may decide to release iOS 15.0.1 before its first significant dot update for iOS and iPadOS 15. We've reached out to Apple for comment on the bug, and we'll update this if we hear back.
Article Link: iPhone 13 Users Experiencing 'Unable to Communicate with Apple Watch' Bug With Mask Unlocking
been having this problem. I’ve rebooted my watch and phone several times and also disabled “unlock with iPhone” from the watch passcode settings. Glad to know it’s not just me and hopefully we will have a fix soon
For all of those folks stuck wondering what to do, waiting until 15.0.1 this week or so will probably be it. Hopefully.
Yes same thing. It initially connected then errored out and I had to force restart watch, but now it wont connect at all.
I am just glad it is not just me. At least Apple will know about the issue given how many people are affected.
I played with stuff, signed out of iCloud, restarted, etc. Will now just wait for an update. I wish Apple would just issue a statement that admits there is a bug. Instead there will be a "performance improvements and tweaks" update with no reference to the issue. Oh well.
Airdrop has been working for me on my 13 mini.
I am in the can't unlock iPhone with Apple Watch club, however.
From the logs, looks to me like it is trying to use the same session key as for the old device, which doesn’t work. Setting up as new iphone generates a new session key. That said, the session keys reset themselves periodically, so maybe it all just starts working overnight or tomorrow.