Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
63,194
30,135


Apple today said an issue preventing some iPhone 13 users from using the Unlock with Apple Watch feature will be fixed in an upcoming software update.

iphone-13-apple-watch-bug.jpeg

In a support document, Apple said affected users can turn off Unlock with Apple Watch and use their passcode to unlock their iPhone 13 until the software update is released. The feature, which is designed to let you unlock your iPhone while wearing a mask or ski goggles, can be toggled off in the Settings app under Face ID & Passcode.

Apple did not specify which software update will include a fix, nor did it provide a timeframe. The first beta of iOS 15.1 was released five days ago, but Apple could also choose to release a minor iOS 15.0.1 update with bug fixes.

As we reported, affected users might see an "Unable to Communicate with Apple Watch" error message if they try to unlock their iPhone 13 while wearing a face mask, or they might not be able to set up Unlock with Apple Watch.

Article Link: Apple to Fix Issue Preventing iPhone 13 Users From Unlocking With Apple Watch in Upcoming Software Update
 
Last edited:

dantracht

Cancelled
Sep 19, 2013
1,422
7,944
Now I get that this software is more complicated these days and I get it takes more to get it right. Nevertheless.....there was a time not too long ago when I HAD to have the latest iPhone on launch day. There was also a time not too long ago when the newest iOS was released, pretty much in full, a few days before the new iPhones were released.

Now....it's just different. More and more bugs, more and more features get delayed, and my drive to upgrade just isn't as strong as it once was. My 11PM still works like a champ, and, to be honest, the Pixel 4a takes such amazing photos that now the GF and I are talking about not upgrading until the holidays.

Again, I know I'm being Captain Obvious here and this is just me and my use case, I just think it's wise to wait until this is all ironed out.

As many have said, perhaps switching to every other year release cycles for iOS might not be the worst idea.
 

w5jck

Suspended
Nov 9, 2013
1,517
1,935
I bet if you type the phrase "will be fixed in an upcoming update" into Apple's new Translate feature it will come back as "you are wearing it wrong"!

Apple has become a joke with their total lack of programming skills. If you are an unemployed software developer who can't find a company willing to hire you because you suck at it, then apply at Apple, they will hire you.
 

smoking monkey

macrumors 68020
Mar 5, 2008
2,330
1,460
I HUNGER
Now I get that this software is more complicated these days and I get it takes more to get it right. Nevertheless.....there was a time not too long ago when I HAD to have the latest iPhone on launch day. There was also a time not too long ago when the newest iOS was released, pretty much in full, a few days before the new iPhones were released.

Now....it's just different. More and more bugs, more and more features get delayed, and my drive to upgrade just isn't as strong as it once was.
Totally agree. If you can wait a month or two for your new kit then that is the very best case.
I deliberately ordered a little late so I wouldn't get my 13 on launch day. It's coming in about 3 weeks. Hopefully that's enough time for a few bug fixes and to be aware of all the issues. But with the MBPs if you want built to order I reckon you're gonna have to order asap if you want it before Chrimbo.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.