Updates bring Password Autofill support to 1Password, Dashlane, Keeper and LastPass
Updates to popular iOS titles 1Password, Dashlane, LastPass and Keeper deliver support for Apple's Password Autofill tool, a built-in password management extension that is now open to third-party apps in iOS 12.
With the latest versions of 1Password, Dashlane, Keeper and LastPass, users no longer have to rely on Share Sheets -- or switch between apps -- to fill in password text fields found while browsing the web or in apps that require authenticated logins.
Previously, Password Autofill was restricted to iCloud Keychain, but newly added functionality in iOS 12 allows integration with third-party password managers that implement a credential provider extension.
In practice, the new feature makes information from password managers easily accessible from any app that supports the system-level feature. For example, users can apply information stored in third-party apps to fill in online login forms presented in Safari.
To enable Password Autofill, navigate to Settings > Passwords & Accounts and activate Autofill Passwords. Users can then select which supporting password management apps to enable for autofill duties, including iCloud Keychain.
Once activated, users are able to access password credentials in supporting apps by tapping on Password Autofill -- a small key icon that appears above the soft keyboard -- and selecting information from a desired service. The device authenticates its user via Face ID, Touch ID or PIN code prior to filling in provisioned text fields, such as user name and password.
Password Autofill support for third-party apps is one of many new features included in Apple's iOS 12, which saw release earlier today. The next-generation operating system incorporates marquee features like life management tool Screen Time, advanced augmented reality functionality via ARKit 2.0, Memoji for iPhone X, Siri Shortcuts and more.
With the latest versions of 1Password, Dashlane, Keeper and LastPass, users no longer have to rely on Share Sheets -- or switch between apps -- to fill in password text fields found while browsing the web or in apps that require authenticated logins.
Previously, Password Autofill was restricted to iCloud Keychain, but newly added functionality in iOS 12 allows integration with third-party password managers that implement a credential provider extension.
In practice, the new feature makes information from password managers easily accessible from any app that supports the system-level feature. For example, users can apply information stored in third-party apps to fill in online login forms presented in Safari.
To enable Password Autofill, navigate to Settings > Passwords & Accounts and activate Autofill Passwords. Users can then select which supporting password management apps to enable for autofill duties, including iCloud Keychain.
Once activated, users are able to access password credentials in supporting apps by tapping on Password Autofill -- a small key icon that appears above the soft keyboard -- and selecting information from a desired service. The device authenticates its user via Face ID, Touch ID or PIN code prior to filling in provisioned text fields, such as user name and password.
Password Autofill support for third-party apps is one of many new features included in Apple's iOS 12, which saw release earlier today. The next-generation operating system incorporates marquee features like life management tool Screen Time, advanced augmented reality functionality via ARKit 2.0, Memoji for iPhone X, Siri Shortcuts and more.
Comments
Edit: I’m guessing I need the latest 1Password. Another reason to consider upgrading.
The update did turn up, shortly after I posted that. Still, it can be confusing when you seem to be running the latest version, but the features it's supposed to have don't show up.
It's working now, which should make a lot of stuff less irritating, although the 2FA log ins will continue to be a pain.
Best upgrade ever.
2) Perhaps iOS 13 will bring more evolved APIs that will allow for the one-time code to be added automatically, like it does for Apple's codes; but that may require 3rd-parties to send you the code via iMessage to a specific device, which is possible now that they have business chat.
I bugged this with Apple three years ago. It's a duplicate of another bug, and both mine and the original are still not fixed.
It's something in my account/password data that causes it, and I can't understand why Apple can't simply catch such exceptions and handle them appropriately? It's not a priority, I understand, but when they release a new feature in iOS that touches on this area, surely they should take a look at such bugs?
This might be one of those cases where a reset is needed.
By the way, as a developer, I’m going to point out that nothing useful ever came out of a requirement “to catch an exception and handle it appropriately”.
They don't need my actual password data. Apple receive crash reports for their apps, so it makes sense that they will have the stack trace, and can probably catch such an exception. I haven't got any third party accounts setup. Never added any. What's in that screen? I don't think I've ever been able to see it.
As this password and account data is shared with Safari, whenever I use Safari on iOS I also cannot tap the "Other Passwords..." option, as it crashes Safari.
It also happens on my iPad, too, so what do you want me to reset?
By the way, as a developer, too, the requirement wasn't to "catch an exception and handle it appropriately;" it was to fix the specific bug, which is a valid requirement. Catching the exception is part of the development of the fix.
More bright ideas from the peanut gallery....