Apple iPhone 13 users Complain ‘Unlock with Apple Watch’ Feature Not Working, Fix Incoming

0
Apple iPhone 13 series Pro Max

Apple released iOS 15, iPadOS 15 and watchOS 8 for users worldwide earlier this month. The new software updates brought new features and privacy-related improvements for their respective products. However, it looks like along with the new features, the new software updates might also have introduced some new bugs that hamper the user experience. The new iOS 15 update seems to have broken the ‘Unlock with Apple Watch’ feature on the latest Apple iPhone 13 models. Apple introduced the feature earlier this year for users who were required to enter the password every time they wanted to unlock their iPhone with Face ID. The Unlock with Apple Watch feature allowed users to unlock the device quickly without having to enter the password again and again.

The issue, which was reported by MacRumors, shows the ” Unable to communicate with Apple Watch” error message whenever a user tries to unlock their iPhone using the Apple Watch. The company has acknowledged the issue. On its support page, Apple said that it is currently working on a fix and a new software update will be released soon. 

“Apple has identified an issue where Unlock with Apple Watch may not work with iPhone 13 devices. You might see “Unable to Communicate with Apple Watch” if you try to unlock your iPhone while wearing a face mask, or you might not be able to set up Unlock with Apple Watch,” the company said. It further stated that users can temporarily disable the feature and use their iPhone’s passcode to unlock the device until Apple releases a software update to fix the issue.

Users can turn off the feature by going to Settings > Face ID & Passcode and then tap on the “Unlock with Apple Watch” toggle.

There is no word on the timeline of this new release that will fix the bug. Apple could roll out the patch in iOS 15.1, which is currently in beta. That being said, the company could also release an iterative update (probably iOS 15.0.1) to fix the bug.

Thanks for reading till the end of this article. For more such informative and exclusive tech content, like our Facebook page


LEAVE A REPLY

Please enter your comment!
Please enter your name here