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
Don't get your hopes up, everyone. The latest TestFlight build this week reverts to the behavior nobody wants again.
1P_Dave
Moderator
Moderator1bvr and bkrodgers
Unfortunately, we haven’t yet found a way to work around the conflicts mentioned in the pinned post post due to current iOS AutoFill API behaviour and limitations. We’re continuing to explore options and working closely with Apple to report and identify potential solutions.
-Dave
Is it ok to talk about beta behavior here? For now I'll say this much -- the prior beta build worked pretty much exactly how I want things to work, and I didn't see any negative side effects. Maybe they were there and I didn't run into them. But the behavior we've been discussing here was working fine.
- 1P_Dave
Hi 1P_Dave -- I appreciate your continued engagement on this. I really do.
That being said, I fail to understand why this must be implemented so aggressively in 1Password when the legacy behavior was satisfactory to most, if not all of us, and remains fully functional in iOS 26. Especially if it is understood that using this new Apple Autofill API at this time is causing the "save password" modal prompt to appear after autofilling already-saved credentials, among other user experience challenges and functional limitations of the API in its current form.
I realize that making this significant of a change to the underlying autofill behavior may not be something that can be implemented as an option for users. Though I think it would be welcome as a configurable setting, if that were possible.
I just don't understand why this is seemingly being forced on us now while Apple's API is quite obviously more limited in function compared to 1Password's previous means of handling autofill, and the API is seemingly incomplete or broken at this time. It seems to me that only after Apple has resolved their API issues that this new behavior should be the default or only autofill experience for 1Password.
- 1P_Dave
The challenge is that, without adopting the new save and generate API in iOS 26 and sticking with the old approach, our testing showed that newly generated strong passwords (a feature that is on by default on iOS 26) are not saved to 1Password on iOS 26, creating a real risk of lost credentials which wasn't acceptable.
We recognize there are limitations and issues with the current experience, but sticking with the legacy approach would leave users exposed to these data loss scenarios. Unfortunately, there isn't currently a path that preserves the previous behaviour while also avoiding those risks.
Our team continues to actively work on this to improve the experience where possible, and share feedback and findings with our friends at Apple.
-Dave
Thank you for the clarification. That was something I was not aware of before. I haven't encountered that myself, but it does help clarify why this is being approached so aggressively while it's clear that there are issues with the autofill experience.
