More of a surprise interaction with a trick: there was plenty of talk this year about using the Screen Time feature to enable some extra protection in the case of stolen iDevices, in particular using the option to prevent password changes. But one interesting wrinkle I just hit is that the feature also prevents not just passcode changes on a paired Apple Watch, but in what I think might have been an oversight/unexpect interaction on Apple's part it also silently interferes with the setup flow of a brand new watch. As part of getting started you can set a passcode on the watch, and then also use the feature so it doesn't need it except when off your wrist or first put on. I did so, didn't want simple passcode, it asked for passcode twice, everything seemed fine. But then I noticed it wasn't asking for it when I took it off, which was odd, and then a few hours ago got around to try setting up Apple Pay on the watch, and got a "you need to set a passcode first". Huh? And the trying to do so, the setting for wrist was the only one that could be toggled, everything else was greyed out and reset to defaults. It took me a certain amount of headscratching to figure out that it was the Screen Time setting on my iPhone and I had to go turn that off. The watch never gave the slightest indication during brand new setup that there was an issue.
It does make sense in some ways that the same setting there would hit both, but it's more surprising that it'd disrupt entering a passcode at all for the very first time on a brand new device, and do so without any hint of error. Also kind of an interesting peek beneath the hood so to speak, the "prevent all changes to passcode" functionality must be quite low level/early in the chain.
It does make sense in some ways that the same setting there would hit both, but it's more surprising that it'd disrupt entering a passcode at all for the very first time on a brand new device, and do so without any hint of error. Also kind of an interesting peek beneath the hood so to speak, the "prevent all changes to passcode" functionality must be quite low level/early in the chain.