Chenalejandro

Hi! I'm still facing the same issue (I'm using the latest release, @clerk/nextjs 5.0.10).

This issue only happens when I have a custom sign up/sign in page

@BRKalow Here are the steps to reproduce 1. clone the basic create-next-app with clerk integrated: https://github.com/Chenalejandro/clerk-bug my .env.local env values: ``` NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_ZGVsaWNhdGUtbW9yYXktNS5jbGVyay5hY2NvdW50cy5kZXYk # Put your clerk secret key here: CLERK_SECRET_KEY=sk_test_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...

Closing this issue since now we can use the env variable `NEXT_PUBLIC_ALLOW_INSECURE_COOKIES` to disable secure cookies (https://github.com/stack-auth/stack/commit/bd9f2f7daf36cbd489ab9e66c37f6ee8d60c507c)

from my quick test with the latest next.js canary the bug is fixed. We just need to wait next.js 15 to confirm that the bug is gone and close this...

I don't have any idea on how to solve your issue, but just FYI: you can try https://github.com/amannn/next-intl, it has first class support for next.js and it is being used...

Update: Using pnpm patch to revert changes from these two commits fixed the issue: https://github.com/stack-auth/stack/commit/02fa7f7dfac4bf38c8083a72dcb0da6cab45001a https://github.com/stack-auth/stack/commit/9f73738d12f3c0acf16a75d48b83be1454a7d00d

I cannot find the pull request that fixes this issue. I tried running the latest version of stack with the reproduction repo, and the issue still exists.