upvote
So true! And as any sane Apple user or the standard template Apple Support person would have suggested (and as they actually suggest) - did they try reinstalling the OS from scratch after having reset the data (of course before backing it up; preferably with a hefty iCloud+ plan)? Because that's the thing to do in such issues and it's very easy.
reply
Reinstalling the OS sucks. I need to pull all my bank cards out of my safe and re-add their CVV's to the wallet, and sometimes authenticate over the phone. And re-register my face. And log back in to all my apps. It can take an hour or so, except it's spread out over weeks as I open an app and realize I need to log in a dozen times.
reply
There was a magical period. I suspect it ended with the introduction of the Secure Enclave. But maybe it was a little later.

An encrypted iTunes backup of a device was a perfect image. Take the backup, pull the SIM card, restore the backup to a new phone with the sim card installed, and it was like nothing had happened.

No reauthentication. No missing notifications. No lost data. Ever.

It was nice.

reply
Security theatre killed this. Everyone must be assumed to be a moron incapable of living with the consequences of their own choices at all times.
reply
It's not theater. If an attacker can duplicate your device, that's a problem.
reply
Says who? How do you know what’s on my device, how much it matters to me, and what countless other options I have for recourse if that did happen?
reply
> And log back in to all my apps

Isn’t this built in when transferring devices? Are backups different?

reply
Some information stored in Secure Enclave and cannot be pulled out from there by design.
reply
Yeah, that would've been the cleanest experiment
reply
Latest update at the bottom of the page.

"Well, now it's Feb. 1st and I have an iPhone 17 Pro Max to test with and... everything works as expected. So it's pretty safe to say that THAT specific instance of iPhone 16 Pro Max was hardware-defective."

reply
That logic is somewhat [1] correct, but it doesn’t say anything about whether all, some, or only this particular iPhone 16 Pro Maxes are hardware-defective.

[1] as the author knows (“MLX uses Metal to compile tensor operations for this accelerator. Somewhere in that stack, the computations are going very wrong”) there’s lots of soft- and firmware in-between the code being run and the hardware of the neural engine. The issue might well be somewhere in those.

reply