I am using Clerk with Next.js15.5.6 on vercel. I am seeing an issue after deployment that seems to be a loop of redirects this issue is not a thing locally and I am wonder why? after login, a user is sent into this redirect loop. https://bfamcooking.com
the expected behavior is that it log a user in and redirect to to the dashboard page.I’m stuck on an indefinite loading spinner, possibly due to an unverified phone number. I entered a fake one and then tried to accept the email confirmation but just see the spinner forever
{
"response": {
"object": "client",
"id": "client_34fgfcFHQUCn3UjUunv6Dc0Zh0g",
"sessions": [],
"sign_in": null,
"sign_up": {
"object": "sign_up_attempt",
"id": "sua_34fgrltrPIjIa1mq6pPot2M69KC",
"status": "missing_requirements",
"required_fields": [
"email_address",
"phone_number",
"username",
"first_name",
"last_name",
"password"
],
"optional_fields": [],
"missing_fields": [],
"unverified_fields": [
"phone_number"
],
In general redirect loops are caused by some of your code thinking you’re logged in and some of your code thinking you’re not.
Session cookies are set in the browser when a response comes back from the server with a Set-Cookie header, and the browser can reject that cookie if the domain configuration for the cookie doesn’t match the current website URL. Since you’re pointing this issue doesn’t not occur locally, it’s possible the browser is rejecting your Set-Cookie header.
If this is happening, you’ll see a little Alert error to the right of the header on your Clerk network response after logging in. I can’t find a screenshot of the cookie rejection, but it’ll be in this spot
thank you for looking at the issue. I have been trying to put out this fire for some time now. I hope to have a fix soon.