Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
If I were to be in charge of iOS development, I would have the user able to allow certain apps to operate while the phone is locked. Namely (and for me, only) my grocery list.

That would be nice. For me, it would be the Audible app. I'd want them to be checking security of apps for which this could be enabled carefully, though.
 
What if someone sitting next to you grabbed your phone swiped to unlock it and walked away with without you knowing? Your watch just gave them access to everything on your phone.

I think this could work if it allowed you to bypass FaceID by double-clicking the Watch's side button, like how it works when giving permission on a Mac to install a piece of software.
 
- Safari is a mess. It freezes, can’t touch anything, your only option is to force close the app an try again.
- Regardless of the app, the keyboard does not show up az 10/8 times.
- I think related to the keyboard issue, but some of the apps freeze when the keyboard should be open. Tweetbot, Safari are just my 2 examples I ran into in the last 10 minutes.
On 14.1 (18A8395) for both my iPhone 11 Pro and iPad Pro 11” Second Gen, updated through ipsw files. Not encountering any of these issues despite running 4 and 5 keyboards on the two devices respectively. Otherwise the ‘whatever’ version of 14.1 is running very smoothly with better overall optimisation than the previous 14.0.1. No obvious hesitancies as in 14.0.1.
 
  • Like
Reactions: gank41
On 14.1 (18A8395) for both my iPhone 11 Pro and iPad Pro 11” Second Gen, updated through ipsw files. Not encountering any of these issues despite running 4 and 5 keyboards on the two devices respectively. Otherwise the ‘whatever’ version of 14.1 is running very smoothly with better overall optimisation than the previous 14.0.1. No obvious hesitancies as in 14.0.1.
I've updated on a iphone 7 as well as my daily use iphone 11 max pro and also haven't seen these issues... must be a case by case issue.
 
I’d love to have seen a point update with a solution to face masks.

Apple has a real opportunity to skip Face ID by verifying if the wearer’s Apple Watch is nearby. The Watch is already a secure authenticated device. When you put on the Watch at home, Face ID on your iPhone verifies you and passes on that security to your Watch. As long as you keep the Watch on, it should be able to unlock your iPhone even if you’re wearing a mask.

it is a nice idea, but it does not work for the simple reason that unless it uses the near proximity sensors (distance), it would allow people nearby you to unlock the phone - not cool.
 
So your argument is that someone is illicitly unlocking hour phone while standing within arms length of you?
If you’re sleeping, your Watch knows that. If you’re being forced to unlock your phone by authorities or a mugger, they can simply point your phone at you. You people are overthinking this.

One more time, what some, myself included, are saying is that the device doesn’t know who’s using it. You’re constantly going on about a device knowing where the other device is. The two are not the same. It’s about who’s using it, not the devices knowing where other devices are. :)
 
Works OK for the Mac, why not the phone.

Users mostly unlock their Mac in private or safe locations. Phones are often unlocked in public. If your data is precious you don’t want an unlocking system that can be used by someone who is mugging you or has coerced you to give them your pass lock.

Before you respond, yes all devices are already unsecured from the user being physically attacked or coerced no matter which security system you use. So there’s no point adding an extra system that doesn’t have any advantage.
 
Then you’re exactly where everyone else is now: you have to punch in your PIN. This would just be an added benefit for those with the Watch. Apple already provides this exact solution with Apple Watch + Mac.

macos-catalina-watchos6-continuity-unlock-mac-hero.jpg




So your point is that you need the newer hardware to take advantage of new features? Okay...

This may actually become a security loophole, and as another user already said that you may not necessarily be the one actually wearing the watch. If the concern is typing a passcode, you'd still need to do this on the watch regardless. The only time you don't need to type your passcode on the watch is if your iPhone is already unlocked, and you have the Watch set to be unlocked by the iPhone. This being said, you'd now see a loop on which device will unlock which device.

For now, the reason why unlock your mac with the watch "somehow" makes sense is because the center of your authentication is still the phone. If for example, I am not wearing the watch and I try to bring it close to my locked Mac, the watch would ask me for a passcode, before it will unlock the Mac. My watch will be able to unlock my Mac if before the mac was locked, I was already wearing my watch, and the wastch has already been unlocked by my phone through the API. If not, I still need to enter my passcode on the watch. So in the end, while it "may" be more convenient to unlock with the 4 digit code on the watch, it poses a potentially less secure process flow.
 
This may actually become a security loophole, and as another user already said that you may not necessarily be the one actually wearing the watch. If the concern is typing a passcode, you'd still need to do this on the watch regardless. The only time you don't need to type your passcode on the watch is if your iPhone is already unlocked, and you have the Watch set to be unlocked by the iPhone. This being said, you'd now see a loop on which device will unlock which device.

For now, the reason why unlock your mac with the watch "somehow" makes sense is because the center of your authentication is still the phone. If for example, I am not wearing the watch and I try to bring it close to my locked Mac, the watch would ask me for a passcode, before it will unlock the Mac. My watch will be able to unlock my Mac if before the mac was locked, I was already wearing my watch, and the wastch has already been unlocked by my phone through the API. If not, I still need to enter my passcode on the watch. So in the end, while it "may" be more convenient to unlock with the 4 digit code on the watch, it poses a potentially less secure process flow.
As with the Mac, it would be an option for the user. You know, those that buy the devices? They should have enough free will to decide if they wanted to use a feature or not.

You need to type the code on the watch once - when you put it on your wrist. Sure you can also, I believe, enable to ask for a passcode all the time, but personally I don't have that enabled. So in the morning, watch on the wrist, insert passcode, and off we go, mac will unlock just by me being around.
 
As with the Mac, it would be an option for the user. You know, those that buy the devices? They should have enough free will to decide if they wanted to use a feature or not.

You need to type the code on the watch once - when you put it on your wrist. Sure you can also, I believe, enable to ask for a passcode all the time, but personally I don't have that enabled. So in the morning, watch on the wrist, insert passcode, and off we go, mac will unlock just by me being around.

I agree. For the Mac it's ok, and I use it too. But the premise of my response to the original post is if the phone gets unlocked by the watch as well. That's where I see the security loophole happening.
 
I'm just wondering if/when we'll get 14.1 OTA, or if we'll have to wait for 14.2 to update our current devices.
Generally after a GM is released, there's either a day to 6-7 days of waiting at that point. Could be today or it could be the 20th...

I'm still thinking there'll be a 14.1.1 release before we get the iPhones 12 in our hands on the 23rd. Maybe the 22nd..
 
  • Like
Reactions: Phuz01
Generally after a GM is released, there's either a day to 6-7 days of waiting at that point. Could be today or it could be the 20th...

Oh, I must have missed that the 14.1 release on the dev portal was a GM. Busy news day yesterday. Fingers crossed for sooner (and that it helps a bit with the battery drain introduced by 14.0.1).
 
The fact that your phone is "nearby" doesn't necessarily mean that you are the one using the phone.

Apple seems to have really good control over the range. Apple Watch unlocking a Mac seems to max out at about 2.5 feet, for instance. So you're giving them too much excuse here. They can come up with something that works, up to and including (I suspect) "needs to be in the same hand."

And all that is without even using the U1.
 
This is a VERY BAD IDEA.

Anyone who wanted to gain access to your phone could do so just by having you standing next to your phone. Like the cops. Or a mugger.

You should try the Apple Watch unlock for MacBook. It's much more precise than you think.
 
You should try the Apple Watch unlock for MacBook. It's much more precise than you think.

The unlock requirement on Mac is that the Mac has to have Wireless turned on (but not necessarily connected to a network, like mine at work which uses ethernet). Somehow the Wifi signals are enough to validate, but no clue how they measure the distance.

My wife knows my passcode on my watch and could put it on and log into my computer at home (not that I hide stuff from her so its OK). At work it is fine because only I have access to my watch and it really increases productivity by not having to type my complicated password all of the time.

I still think it is a bad idea with the phone. A watch is always paired with the phone so there should be some symbiotic connection that would be TECHNICALLY easy to do. But the watch is always in possession and will be locked when removed... there is no physical security like that for the phone. Standing in line a pickpocket could grab the phone and browse through all of data/etc... even if there was a distance limit before it got locked up again. Family is another problem because you can actually trust them (mostly)... but do you really want your mom or friend picking up the phone that fell out of your pocket on the couch and going though your messages?
 
I’d love to have seen a point update with a solution to face masks.

Apple has a real opportunity to skip Face ID by verifying if the wearer’s Apple Watch is nearby. The Watch is already a secure authenticated device. When you put on the Watch at home, Face ID on your iPhone verifies you and passes on that security to your Watch. As long as you keep the Watch on, it should be able to unlock your iPhone even if you’re wearing a mask.

Meanwhile, for those of us with good iPhones, face masks aren't a problem at all. Touch ID works just fine with a mask on. And it even works through nitrile gloves.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.