Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
4 years agov2 Client unable to connect to Desktop App
Hi there. I'm testing out the new v2 cli and it seems to be unable to connect to the desktop app.
I have enabled all the 'developer' settings in the v8 beta app. Any suggestions on how to debug thi...
Former Member
4 years ago@"Justin.Yoon_1P" I think I actually just figured out the issue here. The upgrade instructions here: https://developer.1password.com/docs/cli/upgrade/ clearly indicate
For macOS 1Password CLI 2 has to be moved exactly to /usr/local/bin/op.
The other instruction pages, such as https://developer.1password.com/docs/cli/get-started/ indicate
Install 1Password CLI in the default location: /usr/local/bin.
Without the exactly distinction.
I had installed the cli with nix and home-manager which installs the binary somewhere in /nix and symlinks it to /Users/<my-user>/.nix-profile/bin/.
My guess is that if it's not in /user/local/bin then it can't be verified as an authentic binary for biometric things - similar to how the browser extension won't work if your browser isn't installed in /Applications (ran into that problem too).
I removed the installation with nix and installed with brew and it seems to be working now.
Perhaps the area that outputs the connecting to desktop app: not connected error could add a warning if your op binary isn't in /usr/local/bin.
Anyway. Thanks for the help on this.