-
Notifications
You must be signed in to change notification settings - Fork 19
documentation for InvalidAccessError? #2
Comments
The cryptoParameters.default should be an array:
|
It's actually passing in (Not that you care, but the reason for that is that there will soon be other |
Your code snippet above doesn't pass an array. When I copy your code and make the modification in my comment above to change it into an array then the code runs and I see the makeCredential prompt. |
Sorry, I see what you're saying now... I thought it was already an array. Let me verify and get back to you. |
That did the trick, thanks again and sorry for the silly question. For anyone playing along from home, msCredential docs can be found here (although error conditions are still underspecified, just as they are in the W3C spec -- w3c/webauthn#53 :). |
When running the following code:
I get the result: "promiseResolveSuccess Error: InvalidAccessError". It's not entirely clear to me whether this is because Hello is misconfigured / unavailable; some sort of db error; or something else entirely.
Any hints as to how to resolve this error?
The text was updated successfully, but these errors were encountered: