Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Former Member
2 years agoCLI hangs when requesting items
the cli had been working without issues for a while but about a day ago it began to indefinitely hang when fetching an item.
When I run: op item get XXX --otp --debug
I get:
9:35AM | DEBUG | Session delegation enabled
9:35AM | DEBUG | NM request: NmRequestAccounts
9:35AM | DEBUG | NM response: Success
9:35AM | DEBUG | NM request: NmRequestAccounts
9:35AM | DEBUG | NM response: Success
9:35AM | DEBUG | account not signed in, filter=XXXX latest_signin_user=XXXXXXXXXX
9:35AM | DEBUG | not signed in reason: session file not found
9:35AM | DEBUG | NM request: NmRequestAccounts
9:35AM | DEBUG | NM response: Success
9:35AM | DEBUG | NM request: NmRequestAuthorization
9:35AM | DEBUG | NM response: Success
9:35AM | DEBUG | NM request: NmRequestAccounts
9:35AM | DEBUG | NM response: Success
9:35AM | DEBUG | NM request: NmRequestDelegatedSession
and it just hangs there. Any idea of what could be wrong here?
1Password Version: 8.10.3 (81003012)
Extension Version: 2.15.0
OS Version: macOS 13.2.1 (22D68)
Browser:_ zsh
- deweNew Contributor
@ArunV1P I tested running with
--cache=false
but still get the same issue, hanging on NmRequestDelegatedSession. Which kind of makes sense, since the caching happens after a successful login, right? - deweNew Contributor
Same here, hangs on
NmRequestDelegatedSession
. Usually works after actrl-c
and retry.op version 2.22.0
- JKnockaertNew Contributor
Same issue here
- OP CLI 2.22.0
- MacOS 14.1
- 1Password for Mac 8.10.18 (81018040)
- Former Member
+1, exactly same behaviour. Unlocking through the UI prior to using the CLI command works. Running the CLI command a second time also works. Running it only once hangs.
- Former Member
Same, this happens every time for me unless I unlock the app first. macOS Sonoma 14.0, OP CLI 2.21.0. This is not recent behavior w.r.t. the macOS or OP CLI version history.
6:15AM | DEBUG | Session delegation enabled
6:15AM | DEBUG | NM request: NmRequestAccounts
6:15AM | DEBUG | NM response: Success
6:15AM | DEBUG | NM request: NmRequestAccounts
6:15AM | DEBUG | NM response: Success
6:15AM | DEBUG | account not signed in, filter= latest_signin_user=[...]
6:15AM | DEBUG | NM request: NmRequestAccounts
6:15AM | DEBUG | NM response: Success
6:15AM | DEBUG | NM request: NmRequestAuthorization
6:15AM | DEBUG | NM response: Success
6:15AM | DEBUG | NM request: NmRequestAccounts
6:15AM | DEBUG | NM response: Success
6:15AM | DEBUG | NM request: NmRequestDelegatedSession
- wonnageOccasional Contributor
+1 to this. Latest version of OP CLI (2.21.0) on Ventura 13.5 with 1password 8.10.13. The problem seems to occur when 1Password isn't open. Running the CLI command brings up a popup to allow access; allowing access brings up the 1PW master password unlock screen. However, unlocking here doesn't seem to do anything - the screen goes away and I'm left with the same debug logs as @sagmor:
12:48PM | DEBUG | NM request: NmRequestAccounts
12:48PM | DEBUG | NM response: Success
12:48PM | DEBUG | NM request: NmRequestAuthorization
12:48PM | DEBUG | NM response: Success
12:48PM | DEBUG | NM request: NmRequestAccounts
12:48PM | DEBUG | NM response: Success
12:48PM | DEBUG | NM request: NmRequestDelegatedSession
<hangs forever here>
The workaround is to open the 1password app first, but that seems like an unnecessary step given that you can already pop up the auth window.
- Former Member
Hey @sagmor, thanks for reaching out and sorry for the delay here.
I am not seeing the same behavior at my end, but I'd like to help troubleshoot further.
It has been a while since you posted this, so would you mind downloading the latest version of op CLI and testing with it? If the issue persists with the latest version as well, could you share the output of the same command with the
--cache=false
flag?