Roll back to v3 since Chrome extension for 1P4 not working?
I've posted elsewhere (as have others) about an issue with 1P4 extension for Chrome not filling form fields. There seems to be no fix (at least for me) so I'm wondering if there is a way to roll back to v3 if we purchased via the Apple Store.
This new release has rendered 1Password basically useless for me - at least for the primary way I use it, via the browser extension. If there is no quick fix, and I can't roll back to the version that was working, I'll need to look for an alternate solution. Which is a shame.
FWIW:
Mac OS X 10.8.5
Chrome Version 30.0.1599.69
1Password Extension 4.0.0.23
1Password Desktop App Version 4.0 (400200)
No Sophos, VPN or proxy
Chrome and 1Password in /Applications
Downloaded, installed 1PasswordAutosubmit.pkg and restarted.
Comments
-
I totally feel you. I just upgraded from v3 to a v4 family pack only to find out that v4 stopped working on freeSMUG Chromium which has been my primary browser for quite a while now. I can work without the shiny new v4 version but I expect a newer version to work better not worse so I'm somewhat mad because the fact that it doesn't work due to signing issues (which is completely bogus, BTW: unsigned HQ OSS software beats signed CS crap software any time) is burried somewhat deep in the FAQ section where certainly not everybody will look first and see it before they buy.
0 -
Resolved. I had Sophos installed, but had fully disabled On Access and Live Protection scans. Was still getting the problem. Uninstalled, reinstalled Sophos, re-added 127.0.0.1 to the Web Protection > Allowed Websites. Now the the extension fills fields on click.
0 -
Hi guys,
@airfoil, I'm glad you got it resolved.
which is completely bogus, BTW: unsigned HQ OSS software beats signed CS crap software any time
It has nothing to do with quality of the app, just a confirmation that the browser have not been modified by unauthorized folks. It is up to them to code-sign their browsers. We use the code signatures to ensure the browsers are who they are and that gives us more security for our customers. There is no reason for the OSS groups not to sign their apps; Firefox doesn't seem to have any issues here nor WebKit.
In addition, it's always been our policy that we can only support the official stable browsers, and Chromium has never been considered as such by AgileBits, even in 1Password 3. It just works because it is the same extension framework as Chrome. Now, Chromium and their derivatives have to be signed in order for it to work just as Chrome.
0
