ClerkProvider router navigation fixes and OAuth verification improvements
Fixed navigation handling in ClerkProvider to always use your application's router when provided, preventing internal renderer reloads. Also fixed OAuth account transfers that required verification being reset to sign-in start, and corrected redirect URL forwarding for enterprise SSO connections during sign-up.
Patch Changes
-
Keep Clerk's navigation inside the renderer.
ClerkProvidernow always suppliesrouterPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal/CLERK-ROUTER/VIRTUAL/...path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @jeremy-clerkApplications that worked around this by passing no-op router functions, or by filtering
CLERK-ROUTER/VIRTUALout themselves, can remove those workarounds. -
Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @zourzouvillys
-
Route an OAuth transfer to the sign-up continue step when sign-in uses a native OAuth transport. The callback previously navigated with hash-style URLs (
<sign-up-url>#/continue) that the in-place component router cannot resolve, landing transferred sign-ups on the start card where submitting created a fresh sign-up without the verified external account. (#9530) by @jeremy-clerk -
Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @zourzouvillys
-
Updated dependencies [
28b77ac,46bf7ce,8bc1c9f,17b865b]:- @clerk/shared@4.30.0
- @clerk/localizations@4.15.6
Source: original entry ↗