Forum Discussion

Former Member's avatar
Former Member
4 years ago

v2 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 this?

```
❯ op -v
2.0.0

❯ op account add
Biometric unlock integration with the 1Password app is enabled. Add an account through the 1Password app.

To learn how to add an account to the 1Password app, visit: https://support.1password.com/add-account

❯ op account list
[ERROR] 2022/03/16 13:10:30 connecting to desktop app: not connected
```

nearly all commands return connecting to desktop app: not connected


1Password Version: 8.6.0
Extension Version: 2.3.0
OS Version: 12.3

13 Replies

  • Former Member's avatar
    Former Member

    Hi @jeffutter ,

    We have a few paths in biometric auth that we started logging debug messages for. If you hit any of those paths, it would've logged to stdout in your terminal, so I think the absence of logs can be telling here as well, as it would hint that it never entered some of these error paths.

    While it's good to know you are able to use op with biometric auth disabled, we'll try to get it working for you. I'm going to look into this in detail and also bring in some colleagues who are more familiar with the feature as well, and will provide any updates here.

  • Former Member's avatar
    Former Member

    Hey @"Justin.Yoon_1P" thanks for the help.

    Where may I ask should the debug logs be output? In the console? When I run with --debug it's the same as without.


    ❯ op signin --debug
    [ERROR] 2022/03/18 07:26:33 connecting to desktop app: not connected

    This is on macOS 12.3 on a 16" MBP with a fingerprint reader.

    I did notice one additional bit of information. If I turn OFF "Biometric unlock for 1Password CLI" in the app. I can then sign in

  • Former Member's avatar
    Former Member

    Hi @jeffutter

    I would love to help you out, do you mind trying the op signin --debug command to run the signin process with debug logs?

    Also, what OS are you experiencing these issues on? Does your hardware have a fingerprint reader?