Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
System
4 years agoSuper Contributor
[40] Troubles with biometric unlock (Windows)
This discussion was created from comments split from: CLI 2.0 beta.
Backspaze
4 years agoDedicated Contributor
Just checking in here about the CLI 2.0 beta. I'm using the beta of the Windows desktop app and today I got version 8.5.0-103 installed and found that you'd added a setting for integrating with 1Password CLI. Naturally I began poking around for getting my hands on CLI 2.0 and found https://developer.1password.com/ as well as the https://app-updates.agilebits.com/product_history/CLI2 where I could download it. I ran into an error with the integration with the desktop app when trying to sign in to CLI 2.0. It triggered the Windows Hello prompt but returned the error Invoke-Expression : Cannot bind argument to parameter 'Command' because it is null.. Without the integration with the desktop app, it asks for for my account password and I can sign in just fine.
I figured I should report this and headed to this forum as usual but couldn't find a category for the beta of CLI 2.0. As the documentation I linked to above is public and anyone can download the beta from the change log page I thought there would be a forum category ready. But according to this thread you'll have to be invited either by asking here in this thread or by filling in https://bit.ly/1P21BetaDocs (which also is referenced in the documentation).
So, I guess I should stop writing short novels here and fill out the form and see if I'll get access...?
EDIT: I've filled out the form but for the sake of completeness, I'll just leave the full error message below in case I don't get access to the forum.
[ERROR] 2022/01/26 20:49:17 received unexpected response from 1Password app. Please make sure 1Password CLI and the 1Password app are up-to-date.
Invoke-Expression : Cannot bind argument to parameter 'Command' because it is null.
At line:1 char:19
+ Invoke-Expression (op signin my)
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Invoke-Expression], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.InvokeExpre
ssionCommand