Unable to use 1password for passkey

[jplock]

Whenever I try to register a passkey saved in 1Password, this error message is shown in the UI:

Failed to activate face or touch unlock: credential.response is not an instance of AuthenticatorAttestationResponse

1Password is successfully saving the passkey though.

[ottokruse]

Mmm not the first time we see 1password being idiosyncratic: #94

They inject themselves into the browser, but don't do so fully transparently. You should file an issue with them as well

[jplock]

Strange, it works fine with Safari and 1Password, but not Firefox and 1Password

[ottokruse]

Instead of doing the instanceof checks we could check the interface (duck typing):

amazon-cognito-passwordless-auth/client/fido2.ts

Lines 87 to 94 in d7dda28

	if (
	!(credential instanceof PublicKeyCredential) ||
	!(credential.response instanceof AuthenticatorAttestationResponse)
	) {
	throw new Error(
	"credential.response is not an instance of AuthenticatorAttestationResponse"
	);
	}

amazon-cognito-passwordless-auth/client/fido2.ts

Lines 381 to 388 in d7dda28

	if (
	!(credential instanceof PublicKeyCredential) ||
	!(credential.response instanceof AuthenticatorAssertionResponse)
	) {
	throw new Error(
	"credential.response is not an instance of AuthenticatorAssertionResponse"
	);
	}

[ottokruse]

But as said, you should file this with 1Password as well

[myevit]

I have no issues using 1Password for passkeys. Looks like localized issue. 1Password browser extension issues?

[ottokruse]

You use Firefox too @myevit ?

[myevit]

I use 3: Edge, Crome and Firefox. No issues with all of them with 1Password.
there were some behaviour that browser bypassing 1Password passkey hook and go straight to system passkey UI, but so far I can tell, it is not an issue of your app.

[myevit]

Update: Firefox start to give me credential.response is not an instance of AuthenticatorAssertionResponse error on filling out 1Password passkey. It might be happening long time ago, I do use Firefox only for developing.
What's weird is that it's working on as dev on http://localhost:5173 but deployed to cloud. Edge has no issues.
Windows Hello seems have no issues... Probably some 1Password extension bug.