Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Safari Extension Started Asking For Password For Every Auto Fill [SOLVED]
.
I've been using 1P8 for some time without any auto fill issues. All of a sudden today, the iOS Safari Extension started wanting me to manually enter my password for an auto fill anytime Safari was closed and re-opened. I've always had the "Authorize After" Safari Extension setting set to "1 Week".
I tried disabling the Safari Extension, rebooting the phone and reenabling the Safari Extension. I then tried disabling auto fill on both 1P8 and iOS settings, rebooting the phone and then reenabling. Neither of which worked. I ended up having to completely uninstall and reinstall of 1P8, which was annoying, and that worked.
Is there anything else that can be done if this happens again? Is this a known issue?
1Password Version: 8.9.3
Extension Version: Not Provided
OS Version: iOS 15.6.1
Browser:_ Safari
- 1P_Dave
Moderator
Hello everyone,
I wanted to repost my comment from November 1st:
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)
If you're still experiencing the issue with 1Password 8.9.7 or later and iOS 16.1 or later then, in order to avoid bombarding everyone who posted in this thread with notifications with each post, I've created a new thread here: https://1password.community/discussion/135273/1password-for-safari-asking-for-password-every-time-on-ios-16-1-or-later
This thread is now closed. 🙂
-Dave
- 1P_Dave
Are you running iOS 16.1 on your device? If you are then can you restart your iOS device and then try the following steps:
- Open and unlock the main 1Password app from your home screen.
- Make sure that the Reauthorize After setting is set to 1 Day.
- Open Safari and open any web page.
- Tap on the AA icon and then tap on 1Password. Unlock 1Password for Safari.
- Switch to another app.
- Switch back to Safari and try to fill a login into a webpage.
Are you prompted for your account password? I look forward to hearing from you. 🙂
-Dave
- 1P_Dave
I'm sorry to hear that the issue occurred again on your device but I'm happy that a reinstall resolved the issue. If the issue happens again then I'd like to ask you to create a diagnostics report from your iOS device so that we can investigate further:
Sending Diagnostics Reports (iOS)
Attach the diagnostics to an email message addressed to
support+forum@1password.com.With your email please include:
- A link to this thread: https://1password.community/discussion/comment/663597/#Comment_663597
- Your forum username:
AMonitorDarkly - Please do not post your diagnostic report to the forum. This is for your privacy and security.
The report will be in zip format. Please send the entire file.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
The weird thing for me is 8.9.7 fixed it if I use 1 week for the extension timeout. But not if I use 1 day, which is how I had it set before all this.
WorldIRC I wouldn’t be as concerned if I had to do this right off the bat but that wasn’t the case. When I updated to the latest release the issue disappeared right then and there and worked fine up until today.
The fact that it was working again and then broke (again) leads me to believe that there’s something else still going on. This is exactly how this issue started the last time.
AMonitorDarkly many have reported the full remove and reinstall is needed to fix. Hopefully that’s the last time you see the issue.
This issue started re-occurring for me again today.
I was able to resolve it by doing a complete reinstall but it makes me nervous that this was seemingly resolved and working fine for me after the latest release and then randomly started re-occurring a few days later.
I think the Solved tag needs be removed from this post.
