-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: Stack-auth and Localization Redirection Conflict #239
Comments
So, I've fixed my use-case with some workarounds and route hacking, but I'm still looking for a better approach, if possible. Here's how I did it:
|
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 in big projects like https://nodejs.org. I'm also using it and the afterSignInUrl works flawlessly. |
One solution for this is that we can make all the URLs like |
Thanks for the help. I was also using it before, but decided to move on without a library for that purpose. |
Hey there. If there is no way to predict a localised url yet, I guess it would help indeed. It would also be cool do have the same support for the sign-in and sign-up urls so we don't have to run this hardcoded routing handling in middleware.ts. What do you think? |
That is the idea, I think we are going to rework the redirect process to make it more generalized |
Hey everyone 👋
I’m using stack-auth successfully in my non-localized app, and the localized version works fine without stack-auth. However, after merging both, I’m encountering an issue: after signing in, I’m redirected back to /handler/sign-in instead of the
afterSignInUrl
I’ve defined.Is there any documentation or guidance on handling this scenario? I checked the middleware examples, but they didn’t seem to resolve the issue.
I'm looking to be redirected to the specified
afterSignIn
but localised.Thanks!
The text was updated successfully, but these errors were encountered: