Solved

#ME-271 feedback: Inline menu hidden in Safari on iOS when system AutoFill is enabled

Forum|Forum|3 months ago
March 26, 2026
22 replies
3401 views

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.

Best answer by 1P_Dave

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

Show previous replies

T

Tonetony

OK this is nuts!!! First, I have suffered through this for weeks with no idea what is going on. Reviewing my settings - trying unsuccessfully to figure out if the large array of recent changes in locking options have broken my Safari filling, since I often still see the Safari extension icon in Safari fields, but with it saying it's locked. Trying everything. Turning extension on and off, changing locking, restarting phone, on and on and on.. WITHOUT ONE CLUE that this long-time, ORIGINAL feature of 1Password, the primary feature that has worked for years, has been deliberately removed, leaving users like me BAFFLED and struggling to try something, anything.

I rarely visit these forums since you changed software on it and there are no longer distinct areas where it is obvious where to post something and where to search for something. You have vague tags that aren't used regularly or properly. So, I didn't start searching until last night.

In the old forum, I'd have jumped on this, seeking help, immediately.

The effects of this change are inconsistent. Very often the 1Password icon DOES still appear in fields, but tapping it either does nothing at all, or directs you to unlock 1Password - LEADING ONE TO BELIEVE THE FEATURE STILL EXISTS. You have left the feature in, but deliberately broken it!

Only in the last few days does the icon frequently not appear in fields at all. But that's not consistent - it still often appears.

I actually got the Safari fill to work exactly once, yesterday. So, it hasn't even be shut off reliably.

There was good reason to leave both types of fill enabled - because the system way is the only way to fill in passwords in applications. The Safari way was redundant, in that the fields would autofill but you'd also see the "other" password feature on the keyboard at the same time. The redundancy was the price to pay to use Safari.

Would the older app extension design - in 1Password7 - still be functioning had you not replaced it with a Safari extension?

Why do you still allow the extension to be enabled? Why is there no warning? Like, maybe in the App Store notes when you push out a new release? Or somewhere?

I plan to remove the Safari extension. ARE YOU GOING TO INFORM US WHEN IT IS USABLE AGAIN?? What are your plans?

Edit to add: and what do you mean by: "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." If the Safari extension doesn't work, what are it's additional features?? Do you mean it works if you disable native AutoFill on iOS, so 1Password doesn't work in apps, the extension still works? Please xplain further.

Also: I see someone asked about the prompts to Save password. It has done this now for since I upgraded to 1Password8 - on Mac too. This has baffled me. IT JUST AUTOFILLED an exsiting password, why is it asking me to save it? I always close that - saving the password it already knows can't improve anything, so touching the login or password item would at best update its last modified timestamp which is actually unhelpful and deleterious, and at worst cause other mischief.

1P_Dave

1Password Employee

@Tonetony

Thank you for the feedback and I'm very sorry for the abrupt change. I've shared your feedback with the team and we'll work to improve how we communicate changes like this in the future.

Very often the 1Password icon DOES still appear in fields, but tapping it either does nothing at all, or directs you to unlock 1Password - LEADING ONE TO BELIEVE THE FEATURE STILL EXISTS. You have left the feature in, but deliberately broken it!

Only in the last few days does the icon frequently not appear in fields at all. But that's not consistent - it still often appears.

We've reproduced this on our end as well and we're already testing a fix internally. Once testing is complete we hope to release the fix in a future update to 1Password for iOS as soon as possible.

I see someone asked about the prompts to Save password. It has done this now for since I upgraded to 1Password8 - on Mac too. This has baffled me. IT JUST AUTOFILLED an exsiting password, why is it asking me to save it?

I've seen the "Save Password" prompts on iOS as well and it's also something that our development team is aware of and working to resolve. However, I'd like to investigate the prompts you're seeing on your Mac a little further. Would you mind sending a screenshot of the prompt that you're seeing on your Mac to support@1Password.com so that our support team can take a closer look and advise further?

-Dave

T

Tonetony

I'll keep a lookout for that and send a screenshot next time I run into it.

BTW another odd thing (that I solved) was that disabling the Safari extension on iOS turned it off on Mac, and then re-enabling it on Mac also re-enabled it on iOS. There's a setting to prevent that - on Mac, in Safari Settings > Extensions, turn off Share across devices.

But, I guess your feeling is we should actually leave the Safari extension enabled on iOS, but just ignore it for logins (and use iOS Autofill for that), since the extension should still work to autofill other things, like credit cards?

Thanks!

Z

zackwithak

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

1Password Employee

@zackwithak

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

S

Sir0bin

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?

#ME-271 feedback: Inline menu hidden in Safari on iOS when system AutoFill is enabled | 1Password Community

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

1Password Employee

@Sir0bin

I'm sorry for any confusion caused by the thread merge! We bring related threads together to keep everything in one place, so it’s easier for everyone to follow along and stay up to date without having to track down multiple conversations.

I've replied to your other comment here.

-Dave

A

alihamze

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.

jirsbek

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.

W

WorldIRC

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.

1P_Dave

1Password Employee

@WorldIRC

I'm sorry for the change in how you use 1Password in Safari on iOS. Our development team will continue exploring ways to restore the previous behaviour if a reliable solution becomes available.

-Dave

W

WorldIRC

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.

Cruncher

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!

grovolis21

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.

S

Scottrus71

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.

1

1bvrAuthor

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.

S

Sir0bin

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.

M

Matthew2

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

1Password Employee

@Matthew2

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

1

1bvrAuthor

Don't get your hopes up, everyone. The latest TestFlight build this week reverts to the behavior nobody wants again.

B

bkrodgers

Ugh, yeah, it brought back all the issues. No inline menu again, constant save prompts. The prior build was working perfectly.

Show more replies

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded