1Password for Safari does not work with standalone vaults [iOS Password AutoFill is available]

Hi MattSuda

Thank you for reaching out with your concerns. Standalone vaults will not be part of 1Password moving forward, however, the Password AutoFill feature of iOS continues to be available in 1Password for iOS and is usable by those who have existing standalone vaults:

Use 1Password to fill and save on your iPhone and iPad

You can read more about the future of standalone vaults from one of our founders, Dave, here:

What is the future of local/standalone vaults?

Ben

Yes I understand moving forward standalone vaults won't be supported, but from reading previous messages on this forum, those plans are happening with 1Password 8 and a new separate iOS app. 1Password has broken standalone vault support in the current version. I am not happy with this.

I can no longer use the Safari share sheet extension to easily fill in credit card details or other functions. Yes AutoFill still works, but for anything else I now have to manually go into the app and copy it and then go back to Safari and paste it.

Please restore the old Safari share sheet extension that works with standalone vaults.

The forum messages I've read in the past assured us that 1Password 7 and the current iOS app would still work with standalone vaults for now. That doesn't seem to be the case anymore... with every last update to this version of the iOS app, you are taking existing functionality away hoping that we upgrade to a subscription. I am thinking about a subscription, but I am not ready to move to 1Password 8 just yet especially if the Mac app performance is not up to par with the previous app yet. And updates like this taking every last functional thing away from standalone vaults makes it hard to want to consider a subscription.

Yeah, I'm pretty livid! No where in your entire blog post today does it say standalone vaults not supported. No where does it say a 1password subscription is required. In fact, it touts it as being a "free update". It most certainly is not a free update if you are required to pay a subscription to use it. I just paid the full $70 this year for the standalone mac version of 1password 7 and am not about to have to start paying a subscription just to use this new extension support in iOS. Truly sad. Please stop shafting all of your previous paying customers. I'm extremely frustrated about this as I'd been looking forward all summer to this functionality.. shady!

MattSuda

easily fill in credit card details

Indeed; unfortunately Password AutoFill doesn't handle Credit Cards or Identities like 1Password for Safari does. I've filed this feedback with our development team. Thank you for sharing. I'll keep my eye out for any workarounds or progress on this.

Ben

ref: dev/apple/issues#5491

Did you really have to break this without telling anyone? I’d have held off on my iOS 15 update had I known. Actually wait a sec… I’ve just tested the latest release on iOS 14 and it seems to be gone there too. Brilliant. Great job.

Honestly, to think I used to actively support Agilebits and think they were one of the “good guys”. Now it’s just a case of waiting to see which disappointing decision you’ll make next.

It's nothing more than a matter of greed. We have this very functionality on 1Password7 for macOS which DOES support standalone vaults in the browser extension. There is no reason why they can't offer it to us on iOS/iPadOS, other than greed. This is not a security concern, by any means. I truly hope your development team rethinks this decision and does a 180 to allow the rest of us to enjoy this as well with our standalone vaults. I won't be signing up for your subscription!

I'm sorry for the trouble here. It's not ideal and I wish we were able to make things perfect for everyone.

As mentioned it would have been nicer if we were able to bundle 1Password for Safari into an entirely new app as we wouldn't have needed to make changes in to the existing app and avoid breaking anything. While that would have had many upsides we're not ready to introduce 1Password 8 for iOS to the world yet and so we would have needed to create a 3rd app if we went this way. It's really tricky managing multiple SKUs in the store as there's limitations to what you can do there so we need to keep as few SKUs as possible.

Ideally we would have simply supported all approaches in 1Password for Safari on iOS within 1Password 7 but it's just not something we could pursue. We pushed standalone vaults as far as we could and needed the features of 1Password.com to make today's release possible.

A big part of this stems from 1Password for Safari using a lot of the technology and implementations from 1Password 8, which was completely rewritten from the ground up to take full advantage of our 1Password.com service. You can read all about this decision and why we choose this approach in this mini-essay I wrote in another thread.

That post was written with 1Password for Mac and Windows in mind but many of the points cover iOS and iPad as well. And on the technical side of things, 1Password for Safari is a standalone extension within Safari that needs to live completely within ~6MB of memory (in total, minus ~2MB for some preallocated frameworks).

Furthermore, Safari does its best to protect battery life and keep things snappy as well, so it ensures extensions finish in a timely fashion. Frankly I don’t see how we could have made standalone vaults work there with the same great experience.

I’m sure given enough time and effort we could have found ways to hack support in and been at least partially successful, but with the subpar experience combined with standalone vaults not being included in 1Password 8, we decided to go all in on memberships while designing and implementing support for Safari. And I’m glad we did as there’s no way we could have been here on iOS 15 launch day if we had added any additional requirements.

With that said, it is unfortunate that some of the functions from the old share sheet are no longer available. A lot of the reasons why we are so excited about the new approach in 1Password for Safari is we can do so much more than we were ever able to do in the share sheet. We were extremely limited in functionality there and it showed. While we weren't able to preserve all the features of the share sheet the most important one by far is filling passwords and we made sure that would continue to support that via Password Autofill for both members and standalone vault users.

I hope that helps. Take care and stay safe,

++dave;
1Password Founder

As a follow up I wanted to share a screenshot of the Password Autofill feature on iOS . In some other conversations with users I found not everyone had enabled Password Autofill on iOS and were understandably panicking when they had no autofill to fall back up. For anyone who finds themselves in a similar boat, this article should help.

++dave;
1Password Founder

Seriously, you’re crippling existing 1Password 7 functionality we‘ve been paying in the past in order take make us switch to the subscription.

This move will make me switch to a subscription of a competitor.

Thanks for nothing.

After upgrading to IOS 15 on my iPad and using the latest 1Password version, I am getting the “Standalone vaults are not supported” message in Safari even for filling in userid and passwords. I have Auto-Fill enabled with 1Password selected. From reading the previous comments it sounds like this functionality should still work with a standalone vault (while other auto-fill functionality will no longer work).

Can we get some clarification about what auto-fill functionality should still be working with a standalone vault?

And if we are hitting a bug or setup issue if it isn’t working (i.e. “Standalone vaults are not supported” message)?

Thanks,
Mark