-
Notifications
You must be signed in to change notification settings - Fork 36
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
Dashboard breaks if user is deleted that is currently viewed #416
Comments
What is the network tab output when you try and login? |
Hi @rishabhpoddar Before i got an internal server error for the email verify route. Now it does not even call this route. |
Ok, I could reproduce this.
edit: You can also just remove the user from another dashboard tab. After login, the dashboard makes a call to
and throws error 500. |
I reopen this, because I guess this could be handled and forward the dashboard user to the main view. |
What is the error stack on the backend? Or what is the response body of the 500 error API call? |
The response body is |
core and backend log:
|
Right. Whats the response body of the API call? |
See #416 (comment):
|
right. So this is expected. It's cause you deleted the user in the database and then are trying to take an action on it. I guess the SDK should return a 400 error instead of a 500 error. But what happens if you reload the page after deleting the user? |
I still get error 500, until I remove the userid from the url |
Can you share the HAR file please? |
Hi, after an update to 0.21.0 I could not login into the dashboard. I tried core version 8 and 9 via
registry.supertokens.io/supertokens/supertokens-postgresql:<version>
The logs say:
My docker-compose.yaml:
A downgrade to v0.20.0 fixes this vor core 8 and core 9.
Edit: I copied the wrong log. Though I saw that also sdk 0.20.0 throws this error but does not break.
The text was updated successfully, but these errors were encountered: