1Password CLI crashes 1Password 8.10.30 BETA

DutchDelight
DutchDelight
Community Member
edited March 28 in Desktop betas (Mac, Windows, and Linux) 
❯ which op
/opt/homebrew/bin/op

❯ op vault list
[ERROR] 2024/03/28 04:59:51 connecting to desktop app: 1Password CLI couldn't connect to the 1Password desktop app. To fix this, update the desktop app to the latest version. If you're still having trouble connecting, restart the app. If you're using version 8.10.12 or earlier of the app, the 1Password CLI binary must be located in /usr/local/bin/op.

❯ tail 1Password_rCURRENT.log
INFO  2024-03-28T04:06:08.078 tokio-runtime-worker(ThreadId(4)) [1P:app/op-app/src/app/backend/unlock.rs:166] Processing unlocked account 32Q[...]ABC
INFO  2024-03-28T04:06:08.962 tokio-runtime-worker(ThreadId(7)) [1P:op-b5-client/src/internal/unauthorized_session.rs:1259] Verifying device secret (MFA) with server...
INFO  2024-03-28T04:06:09.121 tokio-runtime-worker(ThreadId(7)) [1P:op-b5-client/src/internal/unauthorized_session.rs:915] Device secret was verified
INFO  2024-03-28T04:06:09.121 tokio-runtime-worker(ThreadId(7)) [1P:op-b5-client/src/internal/unauthorized_session.rs:933] No new device secret was given as current one is still valid and verified
INFO  2024-03-28T04:06:09.488 tokio-runtime-worker(ThreadId(1)) [1P:data/ext/op-account-ext-syncer/src/lib.rs:262] The B5 Notifier for (32Q[...]ABC) has connected, now monitoring for events.
INFO  2024-03-28T04:06:09.638 tokio-runtime-worker(ThreadId(1)) [1P:op-syncer/src/sync_job.rs:358] synced account 32Q[...]ABC (0.514438666s)
INFO  2024-03-28T04:06:09.639 tokio-runtime-worker(ThreadId(7)) [1P:data/op-file-transfer/src/lib.rs:603] find_and_complete_pending_uploads: '32Q[...]ABC'
WARN  2024-03-28T04:06:09.639 tokio-runtime-worker(ThreadId(1)) [1P:app/op-app/src/app/backend/vault_item_snapshot.rs:44] Detailed vault reporting not enabled for account 32Q[...]ABC, skipping snapshots sync
INFO  2024-03-28T04:06:10.501 tokio-runtime-worker(ThreadId(1)) [1P:app/op-app/src/app/backend/frontend.rs:26] Front end event: window closed
INFO  2024-03-28T04:06:36.083 tokio-runtime-worker(ThreadId(1)) [status:app/op-app/src/app/backend/updater.rs:259] No Beta updates found for 81030011

Any command crashes 1Password and the send report dialogue comes up.

I also tried with a symlink in /usr/local/bin, same result.

1Password Version: 1Password for Mac 8.10.30 (81030011)
Extension Version: 2.26.1
OS Version: macOS 14.4.1 (23E224)
Browser: Not Provided

Comments

  • ZPrime
    ZPrime
    Community Member
    edited March 28

    1Password for Mac 8.10.30 (81030011) [beta]

    op --version
2.26.1

    I initially noticed this when trying to run a brew update (I have homebrew setup with 1P integration in order to access my github credentials for brew search).

    But I'm able to reproduce with a basic op vault list or similar. The 1Password GUI just quits instantly after running the op command with any verb that would involve actually talking to the GUI portion.

    I have not seen this before, but I'm assuming my app recently updated to 8.10.30 so I suspect it is the cause. Pretty sure I was able to use the CLI correctly a day or two ago, because I ran a brew update and I believe that was what brought me up to CLI 2.26.1 (so maybe the CLI version is actually the problem, and not the beta GUI piece).

    I have submitted crash reports when prompted. I'm happy to provide additional debug information if it's helpful, just give me some direction please. :)

    1Password Version: 8.10.30-11 (81030011)
    Extension Version: 2.22.1 (beta)
    OS Version: macOS 14.4.1
    Browser: n/a (Vivaldi)

  • Ryan Parman
    Ryan Parman
    Community Member

    I run into this fairly regularly too.

  • Ryan Parman
    Ryan Parman
    Community Member
    edited March 28

    Context

    • 1Password.app has "Integrate with 1P CLI" enabled. ✓
    • 1Password.app is on beta channel.
    • Using 1P CLI v2.26.1.

    Running a shell script to load my credentials into my shell session.

    Setup

    Here's my .env file:

    GORELEASER_KEY="op://Personal/{uuid}/credential"

    Here's my op script:

    eval "$(op signin --account {account}.1password.com || true)"

# shellcheck disable=2002,2312
eval "$(cat ".env" | op inject | xargs -I% echo "export %")"

    Expected

    The GORELEASER_KEY environment variable would be defined, and whose value would be the credential pulled from 1P.

    Actual

    1Password.app crashed.

    Asked if I wanted to report or ignore, and I chose to report.

    1Password Version: 1Password for Mac 8.10.30 (81030011)
    Extension Version: 2.22.1 (Test Flight)
    OS Version: macOS 14.4.1
    Browser: Safari Tech Preview

  • Dave_1P
    Dave_1P
    edited March 28

    Hello @ZPrime, @DutchDelight, and @Ryan Parman! 👋

    I've merged all of your threads together so that we can keep the conversation in one place.

    I'm sorry that 1Password for Mac is crashing when you use the CLI. I've reproduced the issue on my end and have alerted our development team so that they can investigate this further and work on a fix. Since we can reproduce this on our end, no other reports or logs are needed for now but thank you to those that sent in reports and offered to send more.

    For the time being, you can revert to the stable version in order to avoid the issue: To stop using the beta

    Let me know if you have any questions.

    -Dave

    ref: dev/core/core#28815

  • ZPrime
    ZPrime
    Community Member

    I actually switched to the Nightly build and updated, and the CLI works again. 🙂 I'll drop my channel back down to Beta now so I can land on the next beta release when it pushes.

    I don't mind running beta as an IT worker myself; I originally started doing it so I could get Passkey support sooner. 😉

  • kawaz
    kawaz
    Community Member

    I have been having the same problem since this morning. In my case, I copied /opt/homebrew/Caskroom/1password-cli/2.26.1/op to /usr/local/bin/op and pointed the symbolic link of /opt/homebrew/bin/op to /usr/local/bin/op too This was a workaround.

    I have confirmed that the issue has been resolved in the Nightly build as well.

  • DutchDelight
    DutchDelight
    Community Member

    I actually switched to the Nightly build and updated, and the CLI works again.

    This worked for me, too. Thanks, @ZPrime

  • SamerY1P
    SamerY1P

    Hi @ZPrime, @kawaz, and @DutchDelight,

    Thank you for for reporting the issue and I’m sorry for the inconvenience. Our development team is currently looking into the issue and the good news is that the crashing does not occur in the nightly version, as you all noted. If you’d like to have a more stable experience then you can also switch to the stable release of 1Password by following these steps:

This discussion has been closed.