Apple says it's fixing this glaring iPhone 13 and Apple Watch bug - TechnW3

What you need to know

  • Apple's new iPhone 13 can't be unlocked by an Apple Watch for a ton of people.
  • Apple has confirmed it's aware of the issue and plans a fix for an "upcoming update."

A fix is coming in an "upcoming update."

Early iPhone 13 buyers have seen their excitement tempered by an odd and irritating bug that prevents their Apple Watch from unlocking their new phone. The iPhone went on sale on Friday — by Sunday, Apple had acknowledged the bug and confirmed that a fix is on the way.

The issue is a particularly irritating one and prevents Apple Watches from unlocking iPhones via a system that was put in place to help during the COVID-19 pandemic. That system makes it possible to unlock your iPhone with your Apple Watch when you're wearing a mask and Face ID isn't viable. Except Apple broke it with iPhone 13 and while the bug isn't impacting everyone, a Reddit thread on the matter is growing by the minute.

Apple says it's "identified an issue," however.

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.

This issue will be fixed in an upcoming software update. Until the update is available, you can turn off Unlock with Apple Watch and use your passcode to unlock your iPhone 13.

For now, Apple suggests that those impacted by this bug should disable the Unlock with Apple Watch feature — a particularly strange suggestion considering the problem is that people can't turn it on in the first place.

This whole problem is an unfortunate detractor from the launch of the best iPhone Apple has ever put on sale — let's hope a fix comes sooner rather than later. Apple is already testing iOS 15.1, but I'd expect an iOS 15.0.1 release to arrive much sooner than that.

- TechnW3
from iMore - Learn more. Be more.
via TechnW3

No comments: