Our community is getting an upgrade on July 2nd! 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
This change is so frustrating that I actually created yet another account for these forums just to log in and express my disappointment. I tried to disable the iPad iOS autofill and just use 1P and hit an immediate wall… apps no longer worked with 1P and passkeys in 1P wouldn’t populate from the iPad vault.
Add to that what appears to be a frustrating bug on iOS, iPadOS, and macOS of constantly asking me to save a password that was filled by 1P.
Not a great direction for usability.
Add to that what appears to be a frustrating bug on iOS, iPadOS, and macOS of constantly asking me to save a password that was filled by 1P.
That's the part that gets me. Since everything was working fine beforehand, it really just seems like 1P jumped the gun on implementing some new Apple password manager API functionality that is just woefully incomplete and buggy in iOS/iPadOS 26.x. I feel like basic QA/testing would have caught this, and 1P would have and should have postponed their implementation until Apple fixes their stuff first.
That being said, I will also note that it appears that this has been reversed in the latest TestFlight beta builds. The change notes only call out a generic "we've made general improvements..." message, but the Safari extension seems to have been reverted to its previous behavior. So maybe our feedback has been heard.
Let's hope the reversal makes it to the production channel too!
It started working for me a few days ago, and I'm on the normal build. Between it being broken for like month late last year, and them deciding to disable it with no announcement, it's super great never knowing if the main function of their service that I rely on every day will actually work, and when it doesn't work if it's a bug or a deliberate choice. Just stellar communication from them, no notes.
