okay, i tried again, the cookies are there on gateway.test

ah ok!!

so they must be getting sent in the subsequent API call? if the API domain is https://gatewaybeta.test

nope, thats what weird, if i hit the get url in the browser directly, its working and im able to see the cookies

but in the api call its not sending the cookies

shall i send you a video?

sure. Please do..

this is something that the browser controls entirely.. haha.. so it's expected to work!

after deployment /auth route refresh gives a page not found. Any idea how I can correct this?

You mean the refresh API is giving 404? Is the API being called by the library that’s giving 404 or are you navigating to that via your browser and that’s giving 404?

@dbMI ^

When app loads to /auth path. If the browser is refreshed, get page not found. Is this a React issue?

Can I see the screenshot?

Also, can I see your init function code on the front end and backend?

404 error

This seems to be an error in how you have configured your netlify app

You probably need to tell it to serve your react app for any URL that the user goes to

If you go to / and then click on a button to go to /auth and that works, then there is no issue with how you have setup supertokens. But if this only shows up when you directly go to /auth from the browser, then it’s an issue with netlify routing incorrectly

that's what I thought. Wasn't sure if maybe you ran across this. I pushed app to Vercel and seems to do the same.

Yea. Seems to be an issue with config in netlify / vercel

ok. Seems any route does it when page is refreshed

Yup.

Expected

thanks

Is there somewhere where we can see change log / notes

Maybe a channel in this discord or a blog would be nice

To see what new features are in each update

Yea. I like the idea of a channel on discord. WIll make it for the next one. But for now, you can see the changelog.md file inside the relevant repos.

Hi, I am planning to use supertokens for our new application. Before I start I wanted to make sure I can invalidate other user's token's. I have read documentation and the only thing I found that you can revoke your own session. How about other users? (Block user from system functionality, or user itself wants to kill other than current sessions)

Hey @User you can revoke other user's sessions too: https://supertokens.io/docs/nodejs/session/revokeallsessionsforuser OR https://supertokens.io/docs/nodejs/session/revokesession