You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
When creating a new credential, parseCredentialPublicKey is called with a Uint8Array value of credential.response.getPublicKey(). On iOS and macOS systems (idk about linux), the byte length returned by getPublicKey() is 91 bytes. Your tests also make use of a 91-byte public key (credential.test.ts:14).
The problem is, on windows systems, byte array that is returned by credential.response.getPublicKey() is 294 bytes long (tested on Windows 10 22H2 19045.4529, edge, firefox and brave, all have the same issue). It leads to crypto failing to import key in bytesToCryptoKey function, throwing DataError, which leads to createCredential function failing.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When creating a new credential,
parseCredentialPublicKey
is called with a Uint8Array value ofcredential.response.getPublicKey()
. On iOS and macOS systems (idk about linux), the byte length returned bygetPublicKey()
is 91 bytes. Your tests also make use of a 91-byte public key (credential.test.ts:14).The problem is, on windows systems, byte array that is returned by
credential.response.getPublicKey()
is 294 bytes long (tested on Windows 10 22H2 19045.4529, edge, firefox and brave, all have the same issue). It leads tocrypto
failing to import key inbytesToCryptoKey
function, throwingDataError
, which leads tocreateCredential
function failing.The text was updated successfully, but these errors were encountered: