You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current API for both JavaScript and NodeJS does not support signing out by providing a userID. This will be useful for the Nodejs SDK especially where you send the user id in the request from the client side and then sign the user out on the backend. This will enable you to write custom server side logic.
Example:
Userbase.signOut("user id here").then(() => console.log("user signed out"));
On Node.js let's say you create your first user and then Sign out, then create a second user after.
When you try to sign out the second user that is that is signed in, you get an error thrown that the user is already signed out.
I noticed this because I realised that the Userbase.init(...) function in the Node.js SDK does not return a session like the client side JavaScript SDK does.
This means the Userbase context will always be the same and link to the first user created on every server request from the client
The text was updated successfully, but these errors were encountered:
The current API for both JavaScript and NodeJS does not support signing out by providing a userID. This will be useful for the Nodejs SDK especially where you send the user id in the request from the client side and then sign the user out on the backend. This will enable you to write custom server side logic.
Example:
On Node.js let's say you create your first user and then Sign out, then create a second user after.
When you try to sign out the second user that is that is signed in, you get an error thrown that the user is already signed out.
I noticed this because I realised that the Userbase.init(...) function in the Node.js SDK does not return a session like the client side JavaScript SDK does.
This means the Userbase context will always be the same and link to the first user created on every server request from the client
The text was updated successfully, but these errors were encountered: