SSH Agent Error: "error: Error: AppError { error: could not authenticate with ssh agent ..."

No update from 1P support? Why? This is a pretty big issue

Same issue here as well -- I also am running an intel mac laptop with touch id, but lid closed, and a paired apple watch attempting to allow confirmation, as was @ghosts. Updating signing key in ~/.gitconfig had no effect.

@hanpq I had exact same issue wihich i "fixed" with installing OpenSSH from Microsoft's (powershell/Win32-OpenSSH) GitHub repository and it's not working at all (but i get rid of that error message :D)

It's now telling me (when I try to sign commits) that I have to have my private keys stored in Private/Personal Vault, where they exactly are. (My Vault has name: Personal)

Other behavior are exactly the same as before:

• ssh-add -L tells that it don't have any identities
• trying to authenticate to servers returns message about that my public key is in invalid format.

Note: I'm currently on beta channel, and I had installed application from production and from nightly channel before as well.

I am now getting another error

sign_and_send_pubkey: signing failed for RSA "" from agent: agent refused operation

Removing the ssh signing seems to have fixed it. FYI I only have one account logged into the client.

I am experiencing the same thing today as well with nothing changing in my setup either.

@ghosts yup, my stacktrace matched yours exactly, down to the line 95 col 37 part.

$ git commit -m "Modified README"
error: Error: AppError { error: could not authenticate with ssh agent, location: Location { file: "ssh/op-ssh-sign/src/ops.rs", line: 95, col: 37 } }

fatal: failed to write commit object

@Foosh135 are you sure the error stacktrace including line number you got matches the stacktrace I posted at the top of the post? I know for a fact that the fix you’re describing isn’t related to what I’m experiencing because it works on and off based on biometric sensor availability (as indicated by the logs).

(Line 95 col 37)

If it does match it could be that the stacktrace just points to the generic error handler they have in their cli.

Hey all, I had the exact same problem as @ghosts, and I was able to fix the problem on my own (without following any of the above suggestions).

Turns out, the public key stored in my 1Pass SSH key didn't match the output of git config user.signingkey for some weird reason.
The fix was to simply open my ~/.gitconfig file and manually replace the value of user.signingkey so that it matched the key stored in 1Pass. After I saved the file and closed it, the problem went away (I was able to authenticate my commits again).

Hopefully this tip will help someone else here!

floris_1P The issue returned... :(

Here are the log messages I'm seeing after it happens:


INFO 2022-10-22T01:07:36.382 tokio-runtime-worker(ThreadId(9)) [1P:foundation/op-sys-info/src/process_information/macos/non_app_store.rs:81] failed to find NSApplication related to pid 3138
INFO 2022-10-22T01:07:36.398 tokio-runtime-worker(ThreadId(1168)) [1P:foundation/op-apple/src/biometry_service.rs:287] System biometry info: BiometricStatus { current_policy: WatchOnly, current_method: TouchId, current_availability: Available }
INFO 2022-10-22T01:07:36.412 tokio-runtime-worker(ThreadId(1168)) [1P:foundation/op-apple/src/biometry_service.rs:287] System biometry info: BiometricStatus { current_policy: WatchOnly, current_method: TouchId, current_availability: Available }
ERROR 2022-10-22T01:07:36.419 tokio-runtime-worker(ThreadId(9)) [1P:op-automated-unlock/src/lib.rs:294] Failed to authorize using system biometry: FailedToUnlockWithKeys(BiometryUnavailable)
INFO 2022-10-22T01:07:36.419 tokio-runtime-worker(ThreadId(9)) [1P:ssh/op-ssh-agent/src/lib.rs:419] Session was not authorized


To add more background: I use my macOS laptop with Touch ID closed and rely on Apple Watch for Biometric sign in. I tried opening the laptop and trying again then all of a sudden it started working (even after closing the lid again, as long as I authenticated with TouchID - maybe because at this point it's cached but when the auth expires it will stop working again). I hope this helps debug the issue.