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

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.

I received more information from Kester at support@1password.com, which doesn't really solve the issues I encountered, but others might find it at least provides useful context:

Apple have recently added a new feature to iOS Password AutoFill that offers to save any login that is used in Safari. This resulted in a conflict between the 1Password integration with iOS Password AutoFill and 1Password for Safari, where iOS would prompt you to re-save any login that was autofilled from 1Password for Safari.
 
The development team here at 1Password have filed feedback with our colleagues at Apple to get this conflict resolved in a future update, but for now, the 1Password for Safari inline menu will be disabled on sign-in forms if the 1Password integration with iOS Password AutoFill is set up. This is to avoid an unacceptable amount of friction that the conflict mentioned would cause in day-to-day use. I'm sorry for any confusion or interruption to your workflow that this has caused and we are working to improve the experience as soon as possible. 
 
In the meantime, you should find that 1Password for Safari will continue to autofill other item types (such as credit cards or identities) without issue, while logins can be autofilled using the 1Password integration with iOS Password AutoFill (by tapping the suggested Logins or the "🔑 Passwords" button that appear directly above your keyboard or at the bottom of the screen). 

I’m glad I found this thread and I’m not going insane!

I have parents in their 70s and trying to help them use 1Password is challenging on a good day. This recent change and the related bugs have made it basically impossible for me to recommend any workflows involving 1Password in a seamless way — we end up resorting to lots of manual copy & paste and switching between apps, and ultimately, just not using 1Password because it's not feasible to learn and adopt this workflow.

I’ve already opened a support ticket #564447 and sent many screenshots and diagnostics there.

Like 1bvr​, I noticed that

nearly every credential that is autofilled by the native autofill in Safari generates a prompt asking me to save the password even though the password is already saved. If I tap "Save," it then offers to "update" the credential in 1Password. But the password being saved is the same password that 1Password just autofilled through the native autofill.

However in my experience detailed in the ticket, when creating a new secure password it actually fails to update an existing credential, with no options displayed under "update existing item" (even though an item was just used for autofill) — the only option being "create new item", which results in exactly what you'd think: multiple 1Password entries for the same login on the same website. And several extra steps/taps for me to teach someone how to open 1Password, search for the duplicate items, check which one has the correct password, and delete the others.

Luckily, finding this thread has given me a temporary workaround that I might not have thought of otherwise: turning off the iOS system setting to "AutoFill Passwords and Passkeys" so far seems to restore the 1Password Safari extension to its old/normal behavior. I fear this may make 1Password unusable in third-party apps, but have not tested this yet as Safari is by far the most common place that we use it.

Here's another vote hoping that this breaking, half-baked change can be rolled back ASAP.

edit: oh, and can this thread be unmarked as "solved"? The recent replies would certainly indicate that the issue has not been solved!

Are you serious? You disabled the core function of your product, and decided the best way to communicate that was in the third bullet point of update notes that no one reads? Been a loyal customer for ~15 years, but this is the last straw. Just cancelled my subscription. Absolutely unacceptable. 

I have to agree that this "feature" is really quite bad. A website I use for work now requires 4 taps when it previously only required 1. Pretty sure he who dies with the least taps wins! Making the experience worse is the offer to save a password that hasn't changed. That seems like a beta test fail if I've ever heard one. Finally, the work website I mentioned earlier still displays the icon to unlock 1Password; however, tapping it unlocks 1Password and does nothing else!?! Not at all confusing. Oh wait, I guess it is confusing since that action used to do something useful.

Given the decision to effectively disable the 1Password extension when using native iOS/iPadOS autofill, how we go about creating Masked Emails through Fastmail now?

I experiencing much of the same issues as mentioned by others above. This very much feels like “cart before the horse”.

The experience is especially worse on iPadOS where using the extension along with Safari meant that I didn’t have to reach for my laptop every time I needed to do something.

I'm sorry but this really is huge UX setback. Now it's practically impossible to use passkeys and Safari extension. To use passkeys "AutoFill from" 1Password has to be enabled but this disables extension's autocomplete feature.

Came here to concur that this new experience is terrible. I cannot state enough how much of a differentiator (read: advantage) the Safari extension has been for 1Password vs. other password managers for me, ever since its launch several years ago. Or let me put it this way: you built an experience that has made me never want to go back to the old way of doing things, let me use it for years, and ripped it away with this update. The whole “you can use it if you disable systemwide autofill” argument is frankly ridiculous, and I consider that to essentially be “we’re taking away the Safari extension” because systemwide autofill is nonnegotiable. All of this could have been avoided with even a toggle, and I beg 1Password to reconsider forcing this on me. 1Password just got considerably more expensive, and taking away a massive reason it was better than other password managers does not sit well with me.

I agree, the new experience is terrible. I’ve also experienced the “save” prompts when the password hasn’t changed. Other issues include:

• being forced to save a new item when I reset passwords, rather than update existing
• after I fix the above and delete the duplicate, then try to login with the new password, it still shows the new entry that’s already deleted. And if I autofill with the corrected entry, it fills the old password instead. 
• overall, the iOS autofill experience is clunky. Having to have it take over the entire screen to unlock is super annoying. Especially with so many sites that separate out entering username and password, so you have to do it at least twice. The inline is so much smoother. 
  
  

if you can work out these glitches and potentially work with Apple to improve the overall autofill experience, I’m all for it. But until then, please make this optional.