Issue with iPadOS 17.6.1 and 1Password Extension on Safari

Hello 1P_Dave ,

With my ipad described in my opening comment and the software levels I am at,
I DO NOT have to force close anything to re-enable the 1Password entension to get it to work again.

1) Go to Safari Entension management (I'm referring to the management icon on the Safari app itself on the same line as the URL. NOT the Safari options referenced from the iPad settings menu)
2)Disable/Reenable 1password entension
3) everything works fine for the first press of the 1password entension as the dialog box appears properly and the autofill will occur properly
4) On the 2nd invocation, however, 1password will not respond when pressing its icon.
5) Other icons such as Raindrop.io will respond
6) So I repeat step 1-2 for every invocation of 1password.

Hi all,

I clear my cache and quit Safari everyday and encounter this issue too. I’m on iPad OS 17.6.1 too.
Like rohanrns, I can confirm that your workaround only works until we keep Safari running.

Thanks.

I have the same problem. Following the steps above fixed the issue, however; I do not regularly force close Safari.

iPad Air M2, iPadOS 17.6.1

rohanrns

Thank you for confirming. I've let our development team know that you're also affected by the issue, hopefully it can be resolved in a future update soon.

In the meantime, there's typically no need to force close an app unless it isn't responding as noted by Apple in their support guide:

Typically, there’s no reason to quit an app; quitting it doesn’t save battery power, for example.

I've shared everyone's reports with the development team.

-Dave

Same issue here since either the last 1P update or 17.6.1 iOS update. And yes, following the above steps does temporarily resolve it.

Hi 1P_Dave

Thanks for your reply and attention to this issue.
Yes, following your steps 1-4 does make the Safari extension on iOS function normally again.
Yes, I do routinely force close safari from the App Switcher as you describe in step 1, this is pretty much normal for me to do several times throughout the day.

Thanks for helping narrow this down, it sounds like a force close of Safari triggers this unique issue and a cycle of disable/enable fixes it until the next force close. Looking forward to your developers finding a permanent fix.

Hello rickapel and rohanrns! 👋

I'm sorry that 1Password for Safari isn't responding on your iOS devices. Our developers are investigating an issue that sounds like it matches the behaviour that you're describing. Can you let me know if the following specific steps allow you to use 1Password for Safari again:

1. Force quit Safari from the App Switcher: Quit and reopen an app on iPhone - Apple Support (CA)
2. Open your iOS Settings and go to Safari > Extensions > 1Password.
3. Disable the setting for Allow Extension, wait a few seconds, and then re-enable it.
4. Re-open Safari.

Can you also tell me if you regularly force close Safari using the method in step 1? From the customer reports received so far, that seems to be triggering the issue.

-Dave

ref: dev/core/core#31962

Same issue. As usual their update breaks something and they’re super slow to fix and respond. Nothing new here.

Yes, iOS devices both on 17.6.1. Both iPads on iPadOS 17.6.1.
All instances of 1Password on 8.10.38.

Trivial to reproduce on both iOS devices, extremely consistent. In my case disable/enable of the extension does nothing, it remains bricked at all times. Rebooting the phone also does nothing to help. Clicking on the lego-piece icon in Safari and tapping 1Password does nothing as well. (Same as the person on reddit).

On both iPads the extension continues to work as it always did, no issues or concerns of any kind.

rohanrns,
Are your iOS and 1Password software levels exactly the same as mine on both your iPhones and iPads?
I'm going to hold off on opening another support ticket with 1password since you did it already. Their support folks also tend to look at these threads and respond accordingly. Maybe you can continue to update this thread if you find the time as you know more. Thanks for the heads up on the Reddit thread also.

I also have a ticket with Apple open. As always, those tickets tend to sit in a dormant state as they expect you open a ticket with the vendor first.

1Password folks are always on the ball so I would expect them to chime in soon on this.

Thanks,
Rick A