IPhone 13 users report errors with Apple Watch unlocking

Error unlocking iPhone 13 with Apple Watch

The arrival of the COVID-19 brought with it many changes in our daily life. One of them is the mask that has been with us since the beginning of the pandemic. However, this accessory limited some actions that we used to do daily, such as unlocking our iPhone with Face ID. In April, Apple launched an unlocking system through the Apple Watch by bypassing Face ID using a second verification system. Users of the new iPhone 13 are reporting problems when using this function and Apple will likely have to release an update soon to fix it.

Errors to unlock iPhone 13 with Apple Watch

Unlock the iPhone with an Apple Watch when wearing a skin. When you are wearing a mask and an Apple Watch, you can lift and look at the iPhone to unlock it. Learn how to set up and use this feature.

The objective of this unlocking system it was clear: avoid using Face ID to unlock the terminal. For this, Apple had to have an external security system to confirm that we are the ones who are going to unlock the iPhone. And this is where the Apple Watch came in that receives a notification when trying to unlock the device. After confirming, we access the springboard without having to remove the mask.

In the last hours users of the new iPhone 13 are having trouble using this feature. When they try to unlock with the Apple Watch they receive an error message:

Unable to communicate with Apple Watch. Make sure the Apple Watch is unlocked and on your wrist, and the iPhone is unlocked.

Related article:
How to unlock your iPhone with a mask and an Apple Watch

Through Reddit some users have managed to understand the reason for this error. The iPhone 13 supposedly generates an unlock key when the process starts and is sent to the Apple Watch to unlock the terminal using that key. However, this error is thrown because iPhone 13 is unable to generate its unlock key and the function is paralyzed and the communication between both devices does not take place.

Apple may need to release an updated version of iOS 15 to solve this problem. It is likely that if Apple considers that it has to be solved as soon as possible, they will consider launching iOS 15.0.1. Otherwise, they would wait for the iOS 15.1 version that would bring back some features like SharePlay that were removed in the final phases of the developer betas.


Follow us on Google News

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: AB Internet Networks 2008 SL
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   Darth koul said

    I have the same problem. I was already waiting for update.

  2.   Antonio said

    It happens to me with a 13 pro max

  3.   Esteban Gonzalez said

    Indeed, I am one of those affected by this problem. I hope they solve it quickly, it is not acceptable that this type of inconvenience occurs in a device of this price.

  4.   Jesus R. said

    They drive us crazy. The entire transfer has been perfect, except for the Movistar eSIM that
    They keep making you go through the box, and the unlocking with a mask that drives us crazy.

  5.   Ivan said

    I solved it by restoring the iPhone and after restoring it as a new iPhone and loaded the backup, all helped by Apple and it works normally for me I have an iPhone 13pro

  6.   Guillem said

    It also doesn't let me configure it to unlock the Mac. I get the same error.

  7.   Belén said

    I did not leave me with the IPhone 13 either !!!! I have tried everything, restore, erase, reset both devices and nothing