Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1Password4 does't work with Chrome in non-standard location #1351

Closed
pyro2927 opened this issue Oct 30, 2013 · 10 comments
Closed

1Password4 does't work with Chrome in non-standard location #1351

pyro2927 opened this issue Oct 30, 2013 · 10 comments

Comments

@pyro2927
Copy link

1Password installed from the Mac App Store can't communicate with Google Chrome when it's installed to ~/Applications.

Number 4 here:
http://learn.agilebits.com/1Password4/Mac/en/KB/filling-issues.html

Is it possible to sim-link to /Applications instead? Possible this is a wontfix, but I thought I'd check.

@phinze
Copy link
Contributor

phinze commented Oct 30, 2013

Ick! I use 1password from cask, so I didn't run across this.

You can change the target symlink dir to /Applications with an option - perhaps that will work?

...stupid mac app store.

@phinze
Copy link
Contributor

phinze commented Nov 1, 2013

I wonder if this was fixed in 4.0.5?

The release notes include "improved sandbox file access code" which seems to be right in the area of this problem.

@nanoxd
Copy link
Contributor

nanoxd commented Dec 6, 2013

@phinze I did some testing on a Mav VM and the issue is still encountered. Symlinking to /Applications yields the same error

@kevinSuttle
Copy link

Yeah this is what it says for me.

screen shot 2013-12-18 at 2 46 53 pm

@phinze
Copy link
Contributor

phinze commented Jan 14, 2014

Good news - the 1password MAS license can transfer to a cask-installed 1password, which should work with a cask-installed Chrome. This should suffice as an official workaround. Less MAS == More Good 🎊 😀

@phinze phinze closed this as completed Jan 14, 2014
@kevinSuttle
Copy link

So is there anything for users to do on their ends?

@phinze
Copy link
Contributor

phinze commented Jan 14, 2014

My (secondhand) understanding is that if you have a working 1password installed from MAS, your License file should automatically work with a cask installed 1password.

If this is not the case, you can switch the license to an Agilebits license by contacting them:

http://learn.agilebits.com/1Password4/1p4-sales-faqs.html#can-i-switch-the-license-i-bought-from-agilebits-store-to-mac-app-store-or-the-other-way-around

@johndbritton
Copy link
Member

As of 1Password 5, iCloud syncing is only available via the Mac App Store distributed version which is unable to fill fields in the Homebrew Cask installed version of Google Chrome.

@vitorgalvao
Copy link
Member

@johndbritton iCloud syncing has always only been available to MAS apps, as far as I know. In addition, as you can see if you read through this issue (and many similar others), there is nothing we can do about it, it is out of our hands.

@johndbritton
Copy link
Member

I was using the Homebrew Cask version of 1Password 4 with iCloud with no troubles for quite some time. I just upgraded to 5 and the feature stopped working.

My post was mostly informational and to improve the likelihood of someone experiencing the problem finding this issue via search.

Full details from AgileBits here: https://discussions.agilebits.com/discussion/30446/icloud-changes-in-the-website-version-of-1password-5#latest

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants