-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bug: (I attempted to deploy the React Kinde app to Vercel) #54
Comments
Hey @thesushilsharma sorry you're having this issue - deployment can be tricky sometimes. Would you be able to share your
|
|
Thanks @thesushilsharma - you said that it's not redirecting to the dashboard - where is it redirecting to instead? |
It redirects to the home page. |
Hey @thesushilsharma, I managed to recreate the issue and solve it with a slight tweak to your
We believe that Hopefully this fixes it for you! |
I attempted to work without using If I remove the redirect function, everything works fine. I can log in and view the dashboard without any issues. However, while localhost works perfectly, something is missing with the redirect, protected route, and dashboard after deploying to Vercel.
|
Hey @thesushilsharma sorry you're still having issues :( We deployed a version of the github repo you sent us here https://basedbrett-two.vercel.app/ which should have working authentication. The code for that is here: https://github.com/peterphanouvong/basedbrett |
Able to redirect to the dashboard after setting isDangerouslyUseLocalStorage={true} Let me know if there is a better solution. |
Prerequisites
Describe the issue
After entering the OTP during the registration.
It is not redirecting to the dashboard or cannot log in with the same credentials.
I check in the Discord community.
But this all works in localhost.
Library URL
https://github.com/kinde-oss/kinde-auth-react
Library version
@kinde-oss/kinde-auth-react": "^4.0.1"
Operating system(s)
Windows
Operating system version(s)
Win 10
Further environment details
No response
Reproducible test case URL
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: