Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It’s not… I set up my iPhone from scratch, and re-paired the Watch (twice) and still have the issue.
Oh that's interesting to know. Most everyone on reddit who had problems had set it up doing transfer (and those who did iCloud or did a full reset with a restore from iCloud) had it working. That sucks that you are having the same issue.
 
Oh that's interesting to know. Most everyone on reddit who had problems had set it up doing transfer (and those who did iCloud or did a full reset with a restore from iCloud) had it working. That sucks that you are having the same issue.

People who know about reddit are people clever enough to use the device-to-device transfer (which goes much faster, especially when using a wire, and which avoids all but a handful of issues where you need to re-login to anything on the new device), I guess.
 
As one of the new proud 13 Pro Max owners, I was reading all up on this issue yesterday. Seems to effect most anyone who upgraded from one iPhone to another using the phone to phone transfer. Sounds like those who set it up using iCloud backup don't have the issue.
My own speculation is that something in that process of going straight phone to phone (which preserves more of your data and passwords than iCloud) screwed something up in the unlock key for the watch. But that's just a guess by me.

Lots of people indicate that wiping their new iPhone and restoring from an iCloud backup fixes the issue, but I've decided I don't care about it enough to have the pain of that step. I'll just wait for the Apple fix (my office doesn't have a mask mandate due to a lower number of employees, so it's only annoying at grocery stores)
I set up with iCloud backup and had the issue. Fixed it though by just backing up and restoring...again
 
I’m saying maybe working from home wasn’t the best solution after all.
Peoples’ productivity may have been up, but I don’t know how one can do an analysis of working from home via number of bugs discovered, made and fixed. We don’t know the entire picture and can’t prove or disprove any speculation…no matter how just or wild it may seem to be.
 
What the heck is up with Apple lately??? They had a year to work on an iterative software update (IOS 15) and even then, they released a buggy pile of poop. Maybe they need to bring their employees back to work ASAP because clearly there’s brain-drain at Apple OR their employees got super lazy working from home…. Everything they’ve released this year has been super-lame.
 
  • Haha
Reactions: Maconplasma
Peoples’ productivity may have been up, but I don’t know how one can do an analysis of working from home via number of bugs discovered, made and fixed. We don’t know the entire picture and can’t prove or disprove any speculation…no matter how just or wild it may seem to be.
No I disagree. Every product released this year seems half-baked. Both hardware and software. They played it safe this year because they could, but the old Apple quality and ingenuity is slowly eroding. There’s an obvious diminishment in terms of stability from bugs across the board in 2021.
 
As one of the new proud 13 Pro Max owners, I was reading all up on this issue yesterday. Seems to effect most anyone who upgraded from one iPhone to another using the phone to phone transfer. Sounds like those who set it up using iCloud backup don't have the issue.
My own speculation is that something in that process of going straight phone to phone (which preserves more of your data and passwords than iCloud) screwed something up in the unlock key for the watch. But that's just a guess by me.

Lots of people indicate that wiping their new iPhone and restoring from an iCloud backup fixes the issue, but I've decided I don't care about it enough to have the pain of that step. I'll just wait for the Apple fix (my office doesn't have a mask mandate due to a lower number of employees, so it's only annoying at grocery stores)
Nope, I used iCloud backup and I’m still impacted by the issue.
 
Ah, some more of that amazing "work from home" they claimed to have as the reason for allowing them to continue to work from home showing its face again. Yikes.

No I disagree. Every product released this year seems half-baked. Both hardware and software. They played it safe this year because they could, but the old Apple quality and ingenuity is slowly eroding. There’s an obvious diminishment in terms of stability from bugs across the board in 2021.

How long have you been using Apple devices, my dudes? General advice for stability has *always* been:

* software: wait for first patch or point release

* hardware: Never buy a first revision

and honestly, while this bug is annoying (including to me personally since it affects my phone and I do tend to upgrade early, even if it means dealing with bugs, because I’m impatient :) ), and shouldn't have slipped through their QA, it’s also not a showstopper. All software has bugs, c’est la vie, Apple will fix this shortly and the majority of people buying a new 13/mini/pro will never see it.

This bug isnt an indictment of WFH, stop trying to shoehorn things into that rhetoric, it’s getting old
 
I restored from backup on my Mac for my new 13 Pro Max. Then I tried to unpair my watch from my old phone and it failed so I had to wipe my watch and restore that too from a back up, quick and easy and I have no issues with my phone unlocking by my watch.
 
I thought it was just something with my settings after upgrading on Friday. Thanks for posting this so I won't waste any more time on it.

Apple needs to have a "new feature" pause year like they did with macOS a few years ago just to get the bugs out of everything.

they won’t because there are so few hardware meaningful upgrades than software upgrades are becoming thz most import part of each year update
 
  • Like
Reactions: centauratlas
If you don't want to wait for a software update, do a backup of your new iPhone 13 (Mac or iCloud), then erase all contents and settings, restore from backup and it would fix it.

A lot of us in the thread in the main forum have confirmed that this works.
 
My wife and I both have this issue. iPhone 12 Pro and 12 Pro Max updated to 13 Pro and 13 Pro Max. Can’t turn on the Watch FaceID feature without the error.
 
Yes, apple never had any bugs like this when Steve Jobs was in charge.

I mean, except for the numerous bugs that happened when he was in charge.

But that wasn’t his fault. Because he was a real man or something. Right?
Exactly
 
I am willing to bet this bug, and many other missing features and bugs are the direct result of so many Apple employees working from home. If this is the price we must pay to keep them safe, along with their families, and the people in their communities I am okay with that.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.