Safari on El Capitan: Plugin doesn't work when 1P is locked

sjcjonker

Hi,

Besides switching from Yosemite to El Capitan I also switched browsers. Chrome => Safari. So it might not be an El Capitan problem. However searching didn't show any similar issues with other users.

My symptoms are that the cmd+\ doesn't work, even pressing the 1P button within Safari doesn't work when Safari was started when 1P was locked.

When I close safari, press 1P Mini in the menubar, unlock, start safari both the button and cmd+\ works fine again.

When the plugin loads the console.app reports the websocket connection, when it fails there doesn't seem to be any agilebits/1password related log entry.

Already tried the removal / wipe at: https://discussions.agilebits.com/discussion/48756/safari-extension-gone-and-deleted

Anybody with the same effects, and maybe a fix :-)?

Tech details:
Hostname : SJC-Mbook
OS Info : Mac OS X - 10.11 - 15A284
HW Info : MacBook8,1 - x86_64
1Password MAS version: 530029
1Password extension from Apple website 4.4.0

---

1Password Version: 530029
Extension Version: 4.4.0
OS Version: 10.11.0
Sync Type: Not Provided

littlebobbytables

Greetings @sjcjonker,

I'm still running Yosemite for the moment but the majority of us here are running El Capitan so we know it does work. The question is what is happening here.

Firstly, try a reboot and see if the issue persists. You'd be surprised what it can solve sometimes and it's an easy enough thing to try.

Next, following a reboot does 1Password mini appear in your OS X menu bar? If it does, I assume it opens the mini lock window if you either click on the icon or use the keyboard shortcut ⌥⌘\. Both of these should work outside the browser. Don't unlock though, I'm just curious to see if the window pops up.

Now, with your vault still locked but that you've confirmed the window appears in the situations above, do you still find that if you click the 1Password Safari Extension icon the lock screen doesn't appear?

We may very well end up asking for a diagnostic report but we'll wait to see what all of that reveals (if anything) and take it from there :smile:

sjcjonker

Greetings @littlebobbytables,

First off all thanks for your response. After my message the new MAS version 540056 was released and instructed me to install the beta extension (4.5.0.b2). This combo seems to have resolved it so far.

For the original post, in the mean time I rebooted twice, as such it was not an issue fixed by a reboot. Nevertheless when it happens again I'll do the tests you mentioned above.

Thx,
Stijn

littlebobbytables

Hi @sjcjonker,

Please do, if it continues we will definitely want to figure out what is going on. Hopefully though things just run smoothly from now on :smile:

Can I confirm that though, something instructed you to install the beta extension?

sjcjonker

Hi @littlebobbytables,

Maybe not a must, but the last blog from agilebits about the convenience edition:

Because this is a brand new way for the various bits of 1Password to talk to each other, it currently requires the beta browser extension. We’d love your help in ensuring that we didn’t break anything. It’s easy: simply use 1Password in your web browser as you normally do, and let us know if something unexpected happens. If you’re interested in helping us out, please install the 1Password beta extension in your web browser and let us know how things are working in our forums. Thanks very much!

So I did :-)

littlebobbytables

Hello @sjcjonker,

So you'll probably laugh at this but the forums have been so busy that I haven't quite caught up on all of our own blog postings so thank you. Yes, I'd better remedy that soonish!

thightower

@sjcjonker

Thanks for posting that. I read the blog post myself. Ok but missed that.

@littlebobbytables

Your not the only one who seemed to have missed that one. ;)

Edit: fixed forum cropped reply, sigh

sjcjonker

@littlebobbytables & @thightower,

Indeed the blog doesn't say it's required. But if you want to mitigate the websocket issue/fake endpoint, which for me is although unlikely something I want to remediate as much as possible. But indeed the blog doesn't state it's required :-)

Stijn

littlebobbytables

Hi @sjcjonker,

If the beta extension works for you then I'm quite happy that you're running it. If you have any problems though please do let us know as it is still technically a beta and that mean possible teething issues. As it stands though it seems to have improved things for you and you can't argue with that :smile: