The experience of using it in the spec is strange: to the user they go through the full registration and it looks like they got a new credential, I see... if my understanding is correct, in this case, the client(browser/mobile os) should return an error instead to create a new credential according to the WebAuthn spec. Can you file this request through Feedback Assistant? I sent Feedback also. FB11943515 But there was not so detailed explanation of the use case. So I will add it!

Can you file this request through Feedback Assistant? I sent Feedback also. https://feedbackassistant.apple.com/feedback/11943515 But there was not so detailed explanation of the use case. So I will add it!

(maybe I missed to submit... sorry if it is duplicated) Thank you for your reply! The experience of using it in the spec is strange: to the user they go through the full registration and it looks like they got a new credential, I see... if my understanding is correct, in this case, the client(browser/mobile os) should return an error instead to create a new credential according to the WebAuthn spec. https://www.w3.org/TR/webauthn-2/#dom-publickeycredentialcreationoptions-excludecredentials

Can you file this request through Feedback Assistant? I sent Feedback also. https://feedbackassistant.apple.com/feedback/11943515 But there was not so detailed explanation of the use case. So I will add it!

Thank you for your reply! The experience of using it in the spec is strange: to the user they go through the full registration and it looks like they got a new credential, I see... if my understanding is correct, in this case, the client(browser/mobile os) should return an error instead to create a new credential according to the WebAuthn spec.