sphardy Posted January 3, 2016 Share Posted January 3, 2016 (edited) Hello While I have seen this issue posted previously and resolved, it appears to have returned. I have successfully used 1Password with Alfred for a number of years, but it has 'stopped working' for me recently - the 1Password bookmarks are not loaded into Alfred and instead I see the error "unable to find 1password data" in Alfred Settings -> Features -> 1Password (Red text in lower right of window) I have the "Enable 3rd party app integrations" option turned on in 1Password and I have the bookmarks-default.json generated in the expected location: ~/Library/Application Support/1Password 4/3rd Party Integration/bookmarks-default.json In Alfred I have tried both enabling autodiscovery and also entering the above path manually, but the "unable to find 1password data" error remains Software versions reported as follows: Alfred 2.8.1 (425) 1Password 6 Version 6.0.BETA-2 (600002) OSX 10.11.2 I appreciate I am using a beta, however I have seen no references anywhere to Agilebits changing their 3rd party integration support and have successfully run with their betas before. I would appreciate any suggestions Edited January 3, 2016 by sphardy Link to comment Share on other sites More sharing options...
Tom Hightower Posted January 3, 2016 Share Posted January 3, 2016 (edited) Just a point of reference for anyone involved, a discussion is active in the 1Password forums Located @ https://discussions.agilebits.com/discussion/54377/login-item-updates-from-all-vaults-clears-3rd-party-integration-file-for-alfred-etc-now-fixed#latest The title of the topic suggests its fixed but it may or may not be (for some) , I, and others still experience the issue. Also manually setting the file location seems to have no noticeable effect. Edit: Add details My specs are the same as sphardy's above. Edited January 4, 2016 by thightower Link to comment Share on other sites More sharing options...
sphardy Posted January 4, 2016 Author Share Posted January 4, 2016 thanks for the pointer - I had missed that post, but gone thru the same debug steps to ensure the bookmark file was being correctly generated. I've added to the thread that I appear to be experiencing the exact same issue. Link to comment Share on other sites More sharing options...
Andrew Posted January 4, 2016 Share Posted January 4, 2016 I'm going to show the automatically discovered path in Alfred's Advanced tab in the next release which should help debug issues such as these. Cheers, Andrew Link to comment Share on other sites More sharing options...
michaelwills Posted January 4, 2016 Share Posted January 4, 2016 I'm going to show the automatically discovered path in Alfred's Advanced tab in the next release which should help debug issues such as these. Cheers, Andrew Thanks much for that @Andrew. I am having the same issue with their latest beta though I hadn't previously. Setting the path directly hasn't helped so I am not sure what data Alfred app sees. The 3rd party file is valid JSON and looks like it is being updated as well. Link to comment Share on other sites More sharing options...
Andrew Posted January 4, 2016 Share Posted January 4, 2016 Thanks much for that @Andrew. I am having the same issue with their latest beta though I hadn't previously. Setting the path directly hasn't helped so I am not sure what data Alfred app sees. The 3rd party file is valid JSON and looks like it is being updated as well. EDIT: This is now available as a pre-release, if you update to 2.8.2 b429 pre-release from Alfred's Update prefs I also made another minor change in this build which may help with the 1Password 6 beta, let me know Cheers, Andrew Link to comment Share on other sites More sharing options...
sphardy Posted January 4, 2016 Author Share Posted January 4, 2016 Hi Andrew New build fixes the issue - I see the enhancement also and that shows Alfred is finding the 1Password file in the 3rd Party Integration folder. Thanks for the fast fix Link to comment Share on other sites More sharing options...
michaelwills Posted January 13, 2016 Share Posted January 13, 2016 Indeed that fix worked. Much obliged! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now