Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
I think you're thinking of Snow Leopard. Which was 12 years ago.

And I agree.

I don't think they've gotten the bugs out since.
 
  • Like
Reactions: centauratlas
It just works

I remember when Steve was alive this wasn't just marketing bs. As is typical with Timmy's Apple, it's just another slogan meaning little.

Just like with their privacy stance
“It just works” never meant “there are no bugs.” It meant “the intended behavior is to do what the user expects.”

There were *tons* of bugs when Steve was in charge.
 
How about fixing safari first, ever since beta 8 it's been terribly slow, App Store update page lags and hangs when refreshing, battery percentage not dropping correctly on iPhone 13 pros and the list goes on.
 
  • Like
Reactions: Premium1
I spent hours resetting repairing my watch the other day.
I enabled the option on my phone during the sync stage and it stuck.
 
  • Like
Reactions: DarkSam
Yay! I wear a mask when inside stores and businesses. That’s my choice and my right don’t know why apple is preventing me from being safe and shopkicking at the same time that’s some discrimination right thur 😂🤣😆

but seriously I do mask up and this is a big help. Can’t wait for the fix. In the mean time I’ll use my passcode
 
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)
 
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)
Yup and that’s the first time I did a phone setup that way. Usually iCloud but I thought why not looks easy. It was easy and it was fast it just broke a feature or two.
Yeah the transfer method seems to be the issue unfortunately. Maybe next year I’ll do iCloud but then it will be some iCloud related bug. Can’t win. 🤨
 
Yup and that’s the first time I did a phone setup that way. Usually iCloud but I thought why not looks easy. It was easy and it was fast it just broke a feature or two.
Yeah the transfer method seems to be the issue unfortunately. Maybe next year I’ll do iCloud but then it will be some iCloud related bug. Can’t win. 🤨
After the two hours it took on mine, I almost did my wife's phone over iCloud (I did mine while at work, I did hers Friday night after I got home) just so that she could use it faster. BUT... I remembered how many things you have to login back into when you do it via iCloud instead of transfer, and decided it was worth the two hour wait (especially where it takes even longer to have everything else slowly come back via iCloud... although you can use your phone sooner).

Still, that seems to be the only thing that it broke, albeit an annoying thing. Hopefully Apple releases the fix this week.
 
  • Like
Reactions: DcGamer05
Maybe it was those developers who want to “work from home” and claim they are more productive and focused. ¯\_(ツ)_/¯
That's one of those things that probably was harder for them to test in beta where it only impacts those with the new iPhone 13 models. I wonder how many employees they have with the new phones in advance to test those things and how that process works. Where it only impacts those who do the iPhone to iPhone transfer of data, who also own an Apple Watch, and who also use the unlock via watch when wearing a mask - there's a chance it was a very small subset of employee testers and it just didn't pop up to be caught. I would hope after this incident, in the future they have new pre-testing steps to add into the process when shipping new iPhones.
 
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.
Agree. In over 30 years of using a Mac, I have never seen a software release as bad as iOS 15. So much has broken and so much "improved" functionality isn't nearly as good as the old. This new Apple mentality of needing yearly updates of everything is only making the software worse and worse. Apple, perfect what you have before something new.
 
After the two hours it took on mine, I almost did my wife's phone over iCloud (I did mine while at work, I did hers Friday night after I got home) just so that she could use it faster. BUT... I remembered how many things you have to login back into when you do it via iCloud instead of transfer, and decided it was worth the two hour wait (especially where it takes even longer to have everything else slowly come back via iCloud... although you can use your phone sooner).

Still, that seems to be the only thing that it broke, albeit an annoying thing. Hopefully Apple releases the fix this week.
I agree. Apple Pay is also one of the worst things to have to re setup. Usually don’t have problems but this year every card put a fraud alert and made me call them taking up lots of time. Not apples fault but annoying nonetheless
 
Well i had the same problem spoke to apple they had no idea how to fix it. I just did a full restore and started without using and old back up problem fixed On my mac and watch. Its a pain having to set it all again from new but fixed most problems i was having.
Still cant use cellular on apple watch as telco still does not support it.
I wish everyone well with the patch that apple will release with all the new bugs.
 
Yup and that’s the first time I did a phone setup that way. Usually iCloud but I thought why not looks easy. It was easy and it was fast it just broke a feature or two.
Yeah the transfer method seems to be the issue unfortunately. Maybe next year I’ll do iCloud but then it will be some iCloud related bug. Can’t win. 🤨
It’s not… I set up my iPhone from scratch, and re-paired the Watch (twice) and still have the issue.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.