Forum Discussion

branok75's avatar
branok75
New Contributor
6 months ago

Passkey on Safari results in error "PublicKeyCredential" after upgrade to Mac OS 15.4

Hi all, after upgrading to Sequoia 15.4, authentication using Passkey (which is required by my employer) ends with error message "TypeError: Can only call PublicKeyCredential.toJSON on instances of P...
browser extension
macos
slessard's avatar
slessard
New Contributor
4 months ago

This is a really sad response from 1Password. To be fair 1Password isn't the only password manager with this bug. The major difference is that other password managers are fixing the issue. Bitwarden has this same bug and the fix on the way. I sure wish 1Password would get it together and fix this bug.

https://github.com/bitwarden/clients/issues/12060

https://github.com/bitwarden/clients/pull/14734

 

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    4 months ago

    slessard​ 

    Thank you for this information, it's very helpful. I've shared this with the team internally. 

    Out of curiosity, did you try the suggestion mentioned here on the page that you linked to and did that allow 1Password to save or sign in using a passkey? 

    -Dave

    • branok75's avatar
      branok75
      New Contributor
      4 months ago

      I can confirm, when I run in Safari Development Mode Console "delete PublicKeyCredential.prototype.toJSON" before clicking on button "Verify Passkey on device <my_device_name>", then clicking on it -> 1Password's "Sign-in with Passkey" popup appeared, again clicking on it (confirmed on phone) and everything worked as before -  I logged in successfully.

      • 1P_Dave's avatar
        1P_Dave
        Icon for Moderator rankModerator
        4 months ago

        branok75 

        Thank you for performing that test. I've passed your comment along to our development team internally. 

        -Dave

  • khaosspawn's avatar
    khaosspawn
    Dedicated Contributor
    4 months ago

    Hi 1P_Dave​ - please can we have some timelines on when this will be fixed. I have to do some really weird "scaning a QR code with my phone" work arounds to login to Oracle sites because 1password doesn't handle this toJSON function properly.

    I've been using 1password since Version 4 in 2013 and I've never seen 1Password sit on this serious an issue for 6 months. Please at least communicate to us when this is scheduled. As more companies go passwordless, and insist on passkeys - this is going to lock people out!

    If the answer keeps being - well use some other browser, use another method - then why am I using 1password? This is such a disappointment from the early days where serious issues like this would be communicated well.

    Please help us!