fix(ui): prevent redirect conflicts between SignIn and SignUp components

[Ayush2k02]

Summary

Fixes redirect conflicts when SignIn and SignUp components are used together on the same page.

Problem

When both <SignIn /> and <SignUp /> components are rendered on the same page (e.g., as tabs in a modal), they interfere with each other's navigation flows. Specifically:

1. User loads a page with both SignIn and SignUp components
2. User attempts to sign in with an email code
3. The sign-in flow navigates to /factor-one
4. The SignUp component's catch-all route matches and triggers RedirectToSignUp()
5. User is unexpectedly redirected to the Clerk domain, losing context

Root Cause

The RedirectToSignIn and RedirectToSignUp components in both SignIn/index.tsx:40-46 and SignUp/index.tsx:21-27 had incomplete dependency arrays:

function RedirectToSignUp() {
  const clerk = useClerk();
  React.useEffect(() => {
    void clerk.redirectToSignUp();
  }, []); // ❌ Missing 'clerk' dependency
  return null;
}

React's exhaustive-deps rule requires including all dependencies used inside useEffect. Without clerk in the dependency array, the effect doesn't properly track when it should run, leading to unexpected behavior when multiple components share the same router context.

Solution

Added clerk to the dependency arrays in both redirect components:

function RedirectToSignUp() {
  const clerk = useClerk();
  React.useEffect(() => {
    void clerk.redirectToSignUp();
  }, [clerk]); // ✅ Properly tracks clerk instance
  return null;
}

This ensures the redirect only happens when the clerk instance changes, preventing unwanted redirects during navigation in other component flows.

Changes

• Updated RedirectToSignIn in SignIn/index.tsx
• Updated RedirectToSignUp in SignUp/index.tsx
• Added changeset for patch release

Testing

This fix allows:

• ✅ Inline SignIn and SignUp forms to coexist on the same page
• ✅ Multi-step authentication flows to work without cross-component interference
• ✅ Email code sign-in to complete without unexpected redirects

Notes

⚠️ Draft PR - This needs testing with the reproduction case to verify it fully resolves the issue.

Related to issue #7456

[changeset-bot]

🦋 Changeset detected

Latest commit: 5259358

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 12 packages

Name	Type
@clerk/backend	Patch
@clerk/ui	Patch
@clerk/agent-toolkit	Patch
@clerk/astro	Patch
@clerk/express	Patch
@clerk/fastify	Patch
@clerk/nextjs	Patch
@clerk/nuxt	Patch
@clerk/react-router	Patch
@clerk/tanstack-react-start	Patch
@clerk/testing	Patch
@clerk/chrome-extension	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@Ayush2k02 is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.