Safari Extension Not Recognizing 1Password v5 after update to Yosemite 10.10.2

angel910

I'm trying to figure out how to get autofill to work again. I updated to Yosemite 10.10.2 and it stopped working.

I have tried the method of deleting the com.apple.Safari.plist, the Extensions.plist, the Safari Extensions List in Keychain, and the entire safari extensions folder. Then rebooting my Mac but I keep running into the same problem.

I even went as far as uninstalling 1password with the same method above, then reinstalling after the reboot and ran into the same issue.

Is there anything else I can try to resolve this issue?

I'm running 1password v5.1 downloaded from the the Mac App Store and Safari 8.03

Drew_AG

Hi @angel910,

From your screenshot, it looks like the 1Password extension in Safari is unable to communicate with 1Password. It also looks like 1Password mini might not be set to always stay running. Please try this:

• Open the main 1Password app (unlock with your Master Password if prompted)
• Go to the menu for 1Password > Preferences
• Select the General tab and make sure Always keep 1Password mini running is enabled
• Close the Preferences, then go to Help > Troubleshooting > Restart 1Password mini
• Unlock 1Password again with your Master Password
• Restart Safari, then try to use the extension again

Does this help at all? Let us know how it goes, and if it's still a problem we'll take it from there.

angel910

@Drew_AG Still got the same result. I even rebooted my mac to see if that might help but nothing changed.

MikeT

Hi @angel910,

Can you email us your diagnostic report to support+forum@agilebits.com with a link to this thread. Please include your forum name in the email as well, so we can connect you to the posts here.

Let us know here when you sent the email, so we can look for it.

Thanks!

angel910

@MikeT

Ok. Thanks guys.

Just sent the diagnostic report. [Saturday Feb 07 - 5:51PM]

sjk

Hi @angel910,

Thanks for emailing us the report, which was received okay. We'll look it over and respond directly through email so we're not getting wires crossed between here and there. :)

ref: YUY-66938-548

angel910

@Drew_AG @MikeT @sjk Hey guys, has anyone been able to figure this out yet? It's coming up on 2 weeks and I still haven't gotten a response

Drew_AG

Hi @angel910,

Actually, @sjk replied to your email on the same day you sent it (February 7), about an hour later. It sounds like you didn't get his response? If so, please check any junk folders or spam filters to see if it was caught there. Sorry for any confusion about that! If you still can't find his reply, please let us know by posting here, and we can try sending it again. Thanks!

angel910

Hey @Drew_AG

Yeah sorry about that but I can't seem to find it in my email. I would greatly appreciate it if you guys would send it again, if possible.

Jasper

Hi @angel910,

I just re-sent the email. Please let us know if you still don't receive it.

MartyS

I have found that I will get the same issue as @angel910 after I've rebooted Yosemite: not every single time but most of the time. If I launch the 1Password application before I try to use it in the browser everything is fine until the next reboot.

If I had to guess, I'd think that for some reason 1Password Mini isn't automatically launching when I login so the Safari extension gets "confused" and needs to get help getting things connected. My copy of 1Password isn't located in /Applications so maybe that's somehow an impact (although other applications are fine with that setup).

On a side note, I truly wish that 1Password wouldn't insist on forcing 1Password Mini into the menubar when this happens—that's never my desire and it doesn't help since things are already okay by the time it loads.

Drew_AG

Hi @MartyS,

From your description, it sounds like 1Password mini isn't running when you reboot your Mac. The 1Password extension in your browser won't work unless mini is running, or the main 1Password app is open (which is why the extension works if you open the main 1Password app first). If you try to use the extension in Safari when neither 1Password mini nor the main 1Password app are running, that should launch 1Password mini (if something prevents mini from opening at that point, the extension will give you an error).

In the main 1Password app, please go to Preferences > General and make sure the option for Always keep 1Password Mini running is enabled. If you don't want to see the 1Password mini icon in your Mac's menu bar, you can uncheck the option for Show mini app icon in the menu bar.

You also mentioned the main 1Password app is not in the Applications folder on your Mac. If the above suggestions don't help, try moving it to Applications and restart your Mac to see if that helps.

Please let us know how it all goes and if you have more questions about that. Thanks!

MikeT

Hi @MartyS,

Just a silly question after reading Drew's post, did you already configure 1Password to run all the time and not to show up in the menu bar but it still won't do it? It sounds like the preference file may be read-only or cached incorrectly by Yosemite where 1Password still has the old values regardless of what you set in 1Password's Preferences. That could explain why 1Password mini isn't running, it was set not to despite the option to do so.

Please let me know if that sounds like it.

MartyS

As you suspect @MikeT, I have my preferences set to always have 1Password Mini run and to not show it in the menu bar. For as far back as I can remember these settings existing… probably forever. Could it be cached incorrectly—I suppose something could have become corrupted along the way. Stranger things have happened. That's why I still would welcome Publisher's House with a truckload of cash at my doorstep even though I don't return their prize entry forms.

defaults read shows the expected values for KeepHelperRunning (1) and ShowStatusItem (0). Since this in theory reads from any existing preferences cache then that's the returned values that should be acted upon. And the fact that if I do launch the 1Password application manually after a reboot (and before I try to use the browser extension) and then quit it, that Mini remains running and I never have the menu bar item for Mini says that the preferences are correct (somewhere).

I'd love to have one of two effects: either Mini always start for me when I login after a reboot, or in those cases where it doesn't/can't that it not put Mini in the menu bar and change the preference setting for the same when it corrects itself as seen by the original poster's screenshot (and what I see too) when it does start.

I'll look at the logs to see what (does not) happen with Mini the next time I reboot (which doesn't happen often).

@Drew_AG Unless there's a technical reason to do so, and there isn't one AFAIK, moving the 1Password application for me personally would be the very last thing I'd do. I mentioned its location only as a very remote possibility. OS X is a system that doesn't require /Applications to even exist—it's just there as a convenience location that I and other long-time users choose to not use for applications that we install ourselves (versus MAS installations).

MikeT

Hi @MartyS,

defaults read shows the expected values for KeepHelperRunning (1) and ShowStatusItem (0). Since this in theory reads from any existing preferences cache then that's the returned values that should be acted upon.

From what I recall on Yosemite, the defaults read read the plist file directly, not the cache that Yosemite is holding.

Would you be willing to move your plist file to the desktop to test this theory? Quit 1Password and its mini, move the plist file to the desktop, reboot (to invalidate the cache, yes, don't ask), open 1Password, and reconfigure the settings. Reboot your Mac once more and see if it runs properly without your help.

Also, can you share the logs with me if you do find anything. I'd suspect the error would be from launchd.

I'd love to have one of two effects: either Mini always start for me when I login after a reboot, or in those cases where it doesn't/can't that it not put Mini in the menu bar and change the preference setting for the same when it corrects itself as seen by the original poster's screenshot (and what I see too) when it does start.

The former is exactly what it is supposed to do, we used the OS X API to register 1Password to the launchctl list. Check your launchctl list to see if it is on the list.

MartyS

My laptop crashed before I could try removing the plist files—don't you hate it when that happens?

This gave me the opportunity to verify that upon reboot, 1Password Mini is not launched and there are no errors to indicate why. So I did a lot of reading and found that what is likely happening to me is that Launch Services has "forgotten" about the bundled launch item, and because I don't have the application in /Applications or ~/Applications it won't be found by the boot/login scanning that automatically happens within those two locations only. So I copied the application to /Applications and launched it from there. I quit and logged out. Upon login Mini was running from its bundle within /Applications as expected. My reading indicated that in addition to those two folders, that the Finder would also detect login item bundles when it copies applications into any folder. So I deleted the version in my private location and copied from /Applications to that other location. When I login now Mini is running from my private location.

So it seems that because I am always getting updated by the updater (and Finder isn't involved) that when the helper login item connection got broken for whatever reason, nothing was going to repair that on its own—not even launching 1Password. Using Finder seems to have done the trick. I hope it holds up and that this note will help someone else in a similar situation! :)

Drew_AG

That's great news @MartyS, I'm glad you were able to figure that all out! Thanks so much for explaining what happened and what you needed to do to solve the problem - I'm sure it will be helpful for others who run into an issue like that. :)