Autofill iOS Input Method
Hi there, the recent blog post highlighted:
Now in beta, we’ve made it possible for you to tap on any input field, access 1Password through the contextual menu, and autofill any login information stored in your vaults.
However this is not working for me on the latest TestFlight (which is the same version # as production)
1Password Version: 8.10.48
_Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Comments
-
8.10.50 is the new test build. I had the same reaction when I read the blog, and then the new build showed up an hour or two later. Give it a bit, it may stagger pushing it out.
0 -
Having said that, it doesn’t seem to actually work. It’s there, I no longer get the not supported pop up. But it just opens a 1P search box, without recognizing the app I’m in, and it doesn’t actually autofill if you select an item. It just opens it in 1P.
0 -
You'll need to tap an individual field to have it autofilled, since this new iOS 18 method only autofills into that specific field you select, rather than the whole form. Let me know if that helps in that case. :)
— Grey
0 -
Somewhat, but with regular auto fill it auto-selects the right login (or at least filter to a list of matches). With this new field-based autofill, it doesn’t. You have to scroll the entire list or search it, and do that each time. Is there really no way to use the context that the other autofill method uses?
0 -
That's right. iOS allows you to use any item in this context, so it doesn't request a specific domain from 1Password like it does when you use "🔑 Passwords" on the keyboard.
Essentially, 1Password doesn't know "where" you are because iOS doesn't tell it, so it shows all items instead.
0 -
That’s kind of a bummer. Really limits its usefulness to the occasional app where the “classic” autofill doesn’t work or pasting the copied MFA codes isn’t allowed. Or am I missing something? I don’t see any advantage over the existing autofill on the keyboard or the safari extension, when they’re an option. I realize this is apple’s limitation, not knocking you. And I’m still glad for you to support it for those edge cases.
0 -
I don’t see any advantage over the existing autofill on the keyboard or the safari extension, when they’re an option.
That's essentially it. Realistically, it's a fallback option. In any case where the "🔑 Passwords" button appears on the keyboard, it'll make more sense to use that because iOS will give 1Password some context about what's going on so that it can suggest the right thing, but this context menu method can be helpful:
- if you want to add something from 1Password to a note or into a message, even something like a private link,
- if the app you're using doesn't prompt iOS to show the "🔑 Passwords" button on the keyboard,
- if you want to copy/paste some credit card details, which iOS's Password AutoFill system doesn't support (but the 1Password browser extension in Safari does!),
- if a one-time password is auto-copied to the clipboard but you accidentally copy something else which overwrites it,
- and similar "huh?" moments where you'd expect to be able to autofill but can't.
It's handy to have when the usual methods fail, but I probably wouldn't use it as the primary method of autofilling.
0
