Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
more_cowbell
3 years agoOccasional Contributor
Safari Biometrics disabled? [SOLVED]
- AMonitorDarklyOccasional Contributor
it's also possible we may need help from our >friends at Apple to bring this back.
I think that’s the biggest concern for myself and others. If 1P ends up having to rely on Apple for a solution then it’s not going to happen. I guarantee Apple doesn’t care about this. As someone else mentioned, they’re going to be more worried about pushing people onto Keychain/Passkeys.
- Jack_P_1P
1Password Team
Hi folks:
I sincerely appreciate your concerns here. I've been a huge user of 1Password for Safari since it released, and I'm having to adjust my workflow here as well.
How and why were these changes just found out recently when iOS 16 has been available for beta testing for months? I can't imagine Apple suddenly made this change in the RC release a week ago.
We noted the issue here in late August, and we've been working on the best solution since then. As it stands, removing Touch ID and Face ID unlock from 1Pasword for Safari is the best path until / unless things change.
you've had months to get this sorted out
As it currently stands, there is no acceptable way to implement Touch ID / Face ID in 1Password for Safari. While the behavior of WebAuthn appears similar between iOS 15 and iOS 16, there are differences, and while we are still actively pursuing a solution, it's also possible we may need help from our friends at Apple to bring this back.
Jack
- shaun3000New Contributor
@alovchin91 yup. They want everyone to have the same experience. Yes they actually said that. 😂
- more_cowbellOccasional Contributor
@ZebraDude if they were truly watching our backs they would have provided a solution before the launch of iOS 16 and we would not have lost yet another feature.
- Former Member
I can’t seem to use biometric unlock on iPadOS 15 either. Did you remove it for all iOS versions? If so, please bring it back for iOS 15 and earlier.
- netnothingOccasional Contributor
Not sure Apple is going to be quick to help out since they would prefer everyone use the built in passwords with iCloud and keychain.
This is an unfortunate change. I can handle the passwords using the auto fill bar, but this means no more auto filling credit card fields without retyping your long master password.
Can’t the 1P auto fill be updated to detect and work with credit card fields?
Anyone have any 1P alternatives that still work? Apple doesn’t save cc data for auto filling do they?
- Former Member
I'm glad that 1Password is watching our backs. I am SO glad that I have held back on updating to iOS 16. I have been a 1Password user since Version 4 for iOS and now an annual subscriber.
iOS 16 is less important for me than 1Password for Safari extension.
- noraarNew Contributor
MrC that is certainly a possibility, but when you get a response like this "We would like to bring back this feature one day and are working closely with our partners at Apple to figure out how to make that happen." from Jack_P_1P it doesn't inspire a lot of confidence in AB actually working on a solution.
The biggest issue with 1Password and AB right now is the frustrating insistence of not giving any clues to future plans and leaving everything vague; thus making users guess as to when and what things might actually get fixed. I understand AB's stance of wanting to under promise and over deliver, but right now AB is promising nothing and still under delivering.
- MrCRespected Contributor
Or maybe one or both sides were trying to find a resolution, and it just didn't make the iOS 16 deadline. It happens. Apple had to delay many iOS 16 features until later (as they did with 15, and 14, ...), and 1Password is obviously drinking through a firehose right now, and likely this issue has only added to it.
- noraarNew Contributor
1P_Ben How and why were these changes just found out recently when iOS 16 has been available for beta testing for months? I can’t imagine Apple suddenly made this change in the RC release a week ago.
Something doesn’t quite add up here - either Apple made a sudden change to WebAuthn in the last week (unlikely) or AB completely dropped the ball on this as you’ve had months to get this sorted out (far more likely).