Wrapping redirect in ClerkProvider leads to spurious redirect #2646
Description
Preliminary Checks
- I have reviewed the documentation: https://clerk.com/docs
- I have searched for existing issues: https://github.com/clerk/javascript/issues
- I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
- This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.
Reproduction / Replay Link
https://github.com/xixixao/bug-clerk-next-redirect
Publishable key
pk_test_cHJvcGVyLXdoaXBwZXQtNzcuY2xlcmsuYWNjb3VudHMuZGV2JA
Description
npm run dev- Sign in or sign up
- Wait a second, and observe that you are redirected to an invalid URL that doesn't live under the configured
basePath
This was super hard to debug, but in the end what I had was weird, basically my layout was at the wrong level. Still wanted to share it in case someone else runs into this. Looks like nesting a redirect, or streaming server component, under ClerkProvider leads to weird behaviors.
Environment
System:
OS: macOS 14.2.1
CPU: Apple M1
Binaries:
Node: 18.17.0 - ~/Library/Caches/fnm_multishells/2125_1705529595263/bin/node
npm: 9.6.7 - ~/Library/Caches/fnm_multishells/2125_1705529595263/bin/npm
pnpm: 8.7.4 - /opt/homebrew/bin/pnpm
Browsers:
Chrome: 120.0.6099.234
Safari: 17.2.1
npmPackages:
@clerk/nextjs: ^4.29.4 => 4.29.4
@types/node: ^20 => 20.11.5
@types/react: ^18 => 18.2.48
@types/react-dom: ^18 => 18.2.18
autoprefixer: ^10.0.1 => 10.4.17
eslint: ^8 => 8.56.0
eslint-config-next: 14.1.0 => 14.1.0
next: 14.1.0 => 14.1.0
postcss: ^8 => 8.4.33
react: ^18 => 18.2.0
react-dom: ^18 => 18.2.0
tailwindcss: ^3.3.0 => 3.4.1
typescript: ^5 => 5.3.3