When 1p lock/unlock, the 1p browser extension blocked other U2F devices.
async function get(options) {
const response = await navigator.credentials.get(options);
response.toJSON = ()=>getResponseToJSON(response);
return response;
}
webauthn-json.browser-ponyfill.js:204 Uncaught (in promise) TypeError: Cannot set properties of null (setting 'toJSON')
at w (webauthn-json.browser-ponyfill.js:204:18)
at async rp (webauthn-create.ts:337:30)
at async rd (webauthn-create.ts:287:5)
Did the 1p QA/QC people do their jobs? Why, the 1p can ship the broken extension twice??
Old Thread.
https://1password.community/discussion/140685/passkey-blocking-login-with-other-physical-key#latest
1Password Version: Not Provided
Extension Version: 2.14.2
OS Version: Not Provided
Browser: Not Provided
