-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix unhandled exception in NAA JS Runtime scenario #7475
Conversation
Reminder: This PR appears to be stale. If this PR is still a work in progress please mark as draft. |
fbdec53
to
c7b2955
Compare
@@ -56,12 +54,6 @@ export function validateCryptoAvailable(): void { | |||
if (!window.crypto) { | |||
throw createBrowserAuthError(BrowserAuthErrorCodes.cryptoNonExistent); | |||
} | |||
if (!window.crypto.subtle) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure it we can safely remove this check as crypto.subtle
is widely used in BrowserCrypto
. cc @tnorling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tnorling assuming you are okay with this.
7a9678c
to
b0af4d9
Compare
To prevent regressions, add a test that simulates JS Runtime environment and tests E2E scenario for NAA. This will fail until #7475 is merged. --------- Co-authored-by: Hector Morales <[email protected]>
There were regressions to the NAA JS Runtime scenario by the following commits, adding new platform API dependencies in the NAA critical path. This change is tested to get JS Runtime back into a working state.