@clerk/ui@1.36.0
Added a dedicated blocked request screen in SignIn and SignUp components with error reference information, and fixed enterprise SSO sign-ins to properly show verification challenges instead of erroring. Improved error handling for protect_check_required scenarios and fixed issues with verification challenge cards spinning indefinitely and sign-ins stranding on "Use another method".
Minor Changes
-
<SignIn />and<SignUp />show a dedicated screen when a request is blocked, with a reference the user can quote to support. (#9600) by @zourzouvillysaction_blockederrors now exposetraceId,title,description,linkUrl,linkText,kindanddataonmeta.
Patch Changes
-
Clear the invitation ticket from the URL when a sign-in completes on a verification challenge. (#9621) by @zourzouvillys
-
Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider. (#9619) by @zourzouvillys
If you use the prebuilt
<SignIn />component, there is nothing to do. If you have Clerk Protect enabled and callsignIn.authenticateWithRedirect()orsignIn.authenticateWithPopup()from a custom sign-in flow, catch aClerkRuntimeErrorwith codeprotect_check_requiredand show the verification challenge, to avoid a stalled sign-in.That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated:
signIn.protectCheckis set, or its status isneeds_protect_check. For enterprise SSO, run the challenge and then callauthenticateWithRedirect()again withcontinueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown. -
Fix the verification challenge card spinning indefinitely when continuing the sign-in after a completed challenge fails. The error is now shown, and "Try again" retries the continuation. (#9620) by @zourzouvillys
-
Fix sign-ins that use an enterprise connection stranding on "Use another method" after a verification challenge, instead of continuing to the identity provider. (#9620) by @zourzouvillys
-
Updated dependencies [
645a532,84ee588,4e538ac]:- @clerk/localizations@4.20.0
- @clerk/shared@4.36.0
Source: original entry ↗