in

Some Apple iPhone 13/Pro phones “failure” and do not support unlocking the screen through Apple Watch

News from IT House September 25 According to 9to5 Mac reports, Apple’s new iPhone 13/Pro series of mobile phones have been on sale, and a large number of users have already obtained real phones and started using them.

However, the unlocking function of Apple Watch is invalid for some new iPhone 13 series users. When trying to turn on the switch, an error message will be displayed.

This feature was launched as early as April this year as a convenient workaround for unlocking your iPhone while wearing a mask.

To enable the Apple Watch unlock function, open the Settings app on your iPhone and look for the “Face ID and Password” setting. Once you turn on this switch, Apple Watch can verify the iPhone as long as the following conditions are met.

  • Face ID detects a mask or mask

  • Your Apple Watch is nearby

  • Your Apple Watch is on your wrist

  • Your Apple Watch is unlocked

  • Passcode is enabled on your Apple Watch

Once you enable this feature, the iPhone will automatically support Apple Watch unlocking the next time you wear the mask. When your iPhone is unlocked, you will receive a tactile feedback notification on your Apple Watch, notifying you that your iPhone has been unlocked by the Apple Watch. Another option is to quickly “lock iPhone” directly from the Apple Watch notification.

However, when many users tried recently, they found that this feature could not be enabled. Attempting to open it will result in an error message. IT Home netizen @0_null also encountered this problem.

“Cannot communicate with Apple Watch. Please make sure that Apple Watch is worn on your wrist and unlocked, and iPhone is also unlocked.”

According to the netizen, Apple supports a call back saying that at present, in addition to the method of backing up the iPhone, then restoring after restoring the factory settings, wait for the firmware!

Given that this seems to be a common problem, it looks like this may be a bug that Apple needs to fix with the next iOS update.

Share this: