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 put, I prefer the browser extension to select credentials for logging in. It handles OTP codes faster and easier than the system autofill in iOS/iPadOS. Instead, using the system autofill requires extra taps, needlessly populates the clipboard with OTP codes, and generates notifications about the OTP being copied to the clipboard that I'm frequently needing to dismiss.
I'm not sure if this is something that can be made optional in the browser extension settings, but I strongly dislike this new behavior and hope that it will be reverted to the previous behavior, or at least made optional.
Thank you.
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
72 Replies
2 months and still not resolved !!!!
1password on iOS / iPadOS is a regretion that feel like 2023Don't get your hopes up, everyone. The latest TestFlight build this week reverts to the behavior nobody wants again.
- 1P_Dave
Moderator
1bvr 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.
Ugh, yeah, it brought back all the issues. No inline menu again, constant save prompts. The prior build was working perfectly.
What is the latest on this has there been an announcement from 1Password on the position on this anywhere I have missed? Because 1Password has become horrible to use on iOS over the last few months.
With the extension not working any more and the constant prompts to update the password you have just filled in. It makes doing anything in Safari horrendous.
- 1P_Dave
I'm sorry for the AutoFill issues that you're running into. Please take a look at the pinned post for more details and let me know if you have any questions.
The prompts to update the password that you just filled is a bug with the iOS AutoFill API and our team has reported the issue to Apple.
-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!
Such a shame you decided to go down this route. 1P having the iOS extension was one of the things that made it standout from other offerings, especially for certain type of people that require domain/sub-domain level autofill filtering.
That's now gone and the experience is worse, with no competitive advantage compared to other offerings. The workaround suggested in this thread requires 3-4 extra taps, while the previous functionality was instant and more intuitive.
It feels like decisions being made in the last couple years, including the move the Electron among other things, are often for the worst, in terms of user experience, consistency and reliability.
With my sub coming to an end soon, maybe it's time to make the time to migrate to something else.This drives me crazy still after 1 Month of use. I loved the inline menu. Disabling Autofill is also not an option because in Apps it is still needed.
Please fix that asap. We need inline back!
The regression in functionality is driving me nuts. The only reason I use 1Password vs. the alternatives is due to Inline functionality within Safari for iOS.
Dave, can your development team not revert back to "the conflict"? It's not like the app was unusable and the consensus here was the experience with "the conflict" is better than where we are left now.
Or...add a toggle in to optionally re-enable the in-line understanding the conflict.
The built in iOS Autofill is not a good enough replacement for this functionality. This is a major regression in UX and I won’t be keeping my subscription if we’re expected to rely on the iOS Autofill. At that point I’ll just use the Passwords app since I already pay for iCloud.
The built in iOS Autofill not only takes extra taps, but is also a much worse experience when I have multiple accounts for the same domain with different services on each subdomain or port. Even something as basic as my item’s name isn’t rendered until 2 menus deep when it pulls up the full 1Password view.
- 1P_Dave
Thank you both for the feedback. Right now, iOS AutoFill doesn’t respect per-site settings when showing login suggestions near the top of the keyboard or bottom of the screen. To see items with your autofill preferences applied, tap the key icon above the keyboard to open the 1Password window.
Because of conflicts with native AutoFill, 1Password only appears in Safari’s inline menu when native AutoFill is turned off. Our team will continue to explore ways to bring back the previous behaviour if a reliable solution is possible.
-Dave
Hi 1P_Dave, yes I'm aware of the key icon but that's still a lot of extra taps vs the 1 tap menu that used to display. Most of the time the flow is now:
- Dismiss the automatic "helpful" "Sign In" prompt iOS displays
- Tap the password field
- Tap the Key icon
- Tap 1Password
- Tap the login item I want to use
Disabling autofill entirely isn't an option either as the 1Password extension only works in Safari, not any other apps (which I know is an iOS limitation, not yours.)
Can we get more details on what exactly this "conflict" is? Seems like there's a decent number of people responding here that prefer the old method despite whatever "conflict" keeps getting mentioned here.
Exactly my case. I also use multiple accounts on same domain/subdomain with diffferent ports and I basicaly need both. Inline autofill in Safari and iOS autofill feature in apps. Now I preffer to have inline autofill enabled and iOS autofill disabled so when any app asks me for credentials I have to manually copy&paste username, password and OTP. So I have to switch to 1Password app three times. Not great UX.
We already have a discussion going here, but that was marked as solved for some reason, when it clearly isn't. What is the timeline for 1Password re-enabling the core function of their product?
Edit: nice, they just combined this thread into the existing one with no comment. The contempt they have for their most dedicated users is palpable.
- 1P_Dave
This update has made the experience in safari so much worse. For me personally the primary issue is that the system autofill does not seem to respect the "Only fill on this exact host" setting. So for all the sites i host on different subdomains. Each with a separate login. Now I cannot quickly login with the correct password. The one offered by the system autofill is almost never correct and then I have to try to find the correct one in a list of about a dozen.
- 1P_Dave
Welcome to the community! Currently, when using iOS AutoFill, settings you’ve chosen for specific hosts won’t be respected for login suggestions shown near the top of the keyboard or the bottom of the screen. To see the list of items with your autofill behaviors applied, tap on the key icon above your keyboard to open the 1Password window.
-Dave
