Skip to main content
September 23, 2022
Question

iOS/iPad OS Safari Extension Issues

Is there a status update or solutions proposed for the following iOS/iPad OS Safari Extension issues:

  1. While the Magic Keyboard is attached to an iPad, selecting Settings launches a new blank tab instead of redirecting to the app. Settings only successfully launches if the keyboard is disconnected. This was originally documented in https://1password.community/discussion/123524/ipados-ios-safari-extension-bug-all-vaults-issue#latest.
  2. The Safari extension does not respect the reauthorization settings specified in the main app, as mentioned in https://1password.community/discussion/133957/ios-safari-extension-locking-itself-every-few-minutes#latest (e.g. despite selecting 2 weeks, the extension prompts for master password randomly after closing of Safari or locking of the iPad/iPhone). Also, Face ID is not an allowable means of reauthorization—only the master password.
  3. The extension references all accounts rather than respecting collections specified in the main app. Not sure if this is a bug or just a feature that still hasn't been implemented.

Any information on the above would be appreciated. Thank you.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided

11 replies

1P_Dave
1Password Employee
1Password Employee
November 1, 2022

Hello folks,

1Password for iOS/iPadOS 8.9.7 was just released and brings back biometric unlock to 1Password for Safari:

You can now use Face ID and Touch ID to unlock 1Password in Safari after updating to iOS 16.1 or later. #17988

I recommend that you update using the App Store. Once you've updated to the latest version that brings biometric unlock back to 1Password for Safari the "timer" issue will be resolved as well. You can find our guide on how to update here: How to keep 1Password up to date

You'll also need to update to iOS / iPadOS 16.1 or later: Update your iPhone or iPad - Apple Support (CA)

I'd like to thank everyone for their patience and understanding while the team worked to resolve this issue. 🙂

-Dave