0.5.3 Error - runtime error: invalid memory address or nil pointer dereference

Options
john_freeman
john_freeman
Community Member

C:\temp\1password\op_windows_amd64_v0.5.3>op.exe signin .1password.com
Enter the password for at .1password.com:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x455260]

goroutine 1 [running]:
github.com/agilebits/op/command.(SigninCommand).Run(0xc0420741c0, 0xc0420503c0, 0x3, 0x4, 0xc04210cda0)
/go/src/github.com/agilebits/op/command/signin.go:111 +0x7c3
github.com/agilebits/op/vendor/github.com/mitchellh/cli.(
CLI).Run(0xc04211a000, 0xc04211a000, 0x0, 0x72dd65)
/go/src/github.com/agilebits/op/vendor/github.com/mitchellh/cli/cli.go:154 +0x171
main.main()
/go/src/github.com/agilebits/op/main.go:22 +0x78


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Comments

  • john_freeman
    john_freeman
    Community Member
    Options

    Follow up information:
    OS: Microsoft Windows [Version 10.0.16299.665]
    op.exe:SHA256(B907106B02A1843D661A9287FAE39F9FD3059954838A51A63839CCF6BDA87828)
    op.exe.sig:SHA256(8CF70BF9EDAB409D558B59EAC58A8B61102F255A3B494F6A944DB021074D56BD)

  • ag_konstantin
    ag_konstantin
    1Password Alumni
    edited September 2018
    Options

    Hi @john_freeman,

    Thank you for reaching out!

    In your example .1password.com you seem to be missing a subdomain – usually the sign-in domain is my.1password.com.

    Although, even with this scenario I seem to be unable to replicate the issue you are having. Nevertheless, could you please try to sign in using full my.1password.com sign-in domain name and let me know if that works? You can just copy and paste an example below:

    op.exe signin my.1password.com [email]

    Also, are you running op tool for the first time? Would you be able to check if you have an existing .op\config file? Its location depends on whether or not you have configured XDG_CONFIG_HOME environment variable.

    Kind regards,
    Konstantin.

This discussion has been closed.