REMINDER: the community is in read-only mode until July 2nd. This is part of our platform upgrade! Learn more in the FAQs →
Forum Discussion
Solved
#ME-271 feedback: Inline menu hidden in Safari on iOS when system AutoFill is enabled
Hello,
I recently noticed that a lot of login forms were no longer showing the 1Password drop-down to select a credential. I believe it is related to this change referenced in the title.
Simply p...
Hello 1bvr! 👋
Thank you for reaching out about this! When 1Password is set as your system autofill provider on iOS, the inline menu in the Safari extension is now hidden to prevent conflicts between the two filling experiences.
iOS 26 introduced enhancements to AutoFill, including support for strong password generation. This allows 1Password to integrate more deeply with iOS, enabling features like creating strong passwords and filling or saving login credentials directly through AutoFill on your iPhone and iPad.
At the same time, we’ve encountered conflicts between iOS AutoFill and the browser extension that don’t currently have a technical solution. We’re working closely with Apple to explore ways to resolve these issues in the future. In the meantime, we’re focusing on making native AutoFill on iOS the primary way to fill, while the Safari extension continues to provide additional capabilities beyond it.
That being said, our team is actively evaluating the situation and keeping an eye on everyone's feedback in order to determine the best path forward. Your experience will help shape how we move forward. We appreciate you taking the time to share it.
-Dave
The native autofill is inferior in so many ways to the behavior of the extension. This is such a downgrade that I am seriously considering migrating to a different platform.
Primary issue, which is really the dealbreaker for me: extension dropdown logic was smart enough to remember recently or frequently used logins for a page. If I am on a page where there are many logins (I have a family plan and many items are shared with me, so there can be 8 or so logins for a website), the extension was smart enough to know which one to suggest. The native autofill seems to have no such functionality and just suggests using some archaic alphabetical or chronological order, because I am constantly having to close the login suggestion, tap the key icon then scroll to find the correct login. This is by far the worst downgrade of the change.
If I could disable native autofill on safari only so I can continue to use the extension login suggestions, I would but I cannot do so because there is no disable granularity. It’s OS-wide or nothing.
Please give us the option to use the extension dropdown / suggestions if we prefer. It’s not like that logic is going anywhere as it’s used in other extensions. Let the consumers choose!
Thank you.
Comments like this one is probably the reason why they were hesitant to implement this feature in the first place. There is nothing 1Pass can do about the behaviour you're describing. Neither about the fact that native autofill is all or nothing. That's all on Apple and I doubt its going to change anytime soon.
I think you misunderstood my complaint / the situation.
They have implemented this feature, despite these limitations to Apple’s native API.
It is on Apple to improve their API. 1Password, however, has decided to lock iOS customers into either using the inferior API, or preventing autofill from functioning in non-browser applications together. That is on 1P, not Apple.
There's nothing they can do to control what Apple suggests in Apple's UI, but they can absolutely refrain from disabling their superior UI that had been working just fine for years — until they decided to implement unfinished/buggy new APIs that Apple made available.
They're not giving us 1Password out of the kindness of their hearts; we are paying customers who have not been able to use (for months now!) the feature that has been the main selling point of 1P vs. other password managers. Several of us have posted here just asking that they just let us choose to use the "confusing" option that suffers from the Apple bug, if they refuse to revert to the working behavior from a few months ago.
Instead, they essentially copy and paste the same non-response, that they're still looking into what can be done despite Apple's bug. Pretty simple: either revert to what was working, or do what your paying customers are asking for, and let us choose to tap "not now" instead of being frustrated by lack of autofill literally every time we see a login in mobile Safari. At least the latter of those two options does not require months of development work. In fact, they had it working in a beta and then reverted the fix!
Yeah I don't disagree and not defending them in slightest (you can check my post history). But, on this specific decision they've explained their reasoning and as a developer myself, I can see why they've done it. Hopefully Apple will do their part and fix their API.
