@rp okay, maybe I got it. so, all of the 4 locations you wanted me to put some logs in actually returned logs. not a problem. but then I continued logging from within ST and in the

this.errorHandler

, right before

if (error_1.default.isErrorFromSuperTokens(err)) {

I logged the error object just to check whether any errors are thrown. well, there is an error. 😄

ST err: Error: The running SuperTokens core version is not compatible with this NodeJS SDK. Please visit https://supertokens.io/docs/community/compatibility to find the right versions
    at Querier.<anonymous> (/var/task/node_modules/supertokens-node/lib/build/querier.js:88:27)

ohhh i see!

however, when I go to

https://supertokens.io/docs/community/compatibility

I got an empty web page...

😄

which core version are you using?

I am not sure I do... in the package JSON file the only ST-related thing I have is

"supertokens-node": "^8.0.1",

what's your connectionURI?

that must be connected to a core that we managed (an older version - when you signed up)

most likely yeah, I signed up quite some time ago... 😄

right. We can update the core version for you if you'd like.

sent you a PM.

Yes, sir! pls, do! 🙂

Until then, you can use

https://try.supertokens.io

as your connectionURI value and it should work

I'l notify you

once the update is done

yes, I prefer to wait for the real deal.

does it take very long time?

Cool.

> does it take very long time? No... it would have been done in a few mins. But since it's saturday night, I might have to wait for our backend dev to be available to upgrade it 🙂

ah, no worries. totally forgot it's Saturday haha

haha

update for my issue: the guys at ST updated the core version running for my managed instance and now everything is fine. 😺 btw @User , I am getting back two cookies -

sAccessToken

and

sIdRefreshToken

while in the docs it says I should get back

sIdRefreshToken

,

sAccessToken

and

sRefreshToken

.

Oh. Can I see the response headers please?

From the login requests

yes.

message has been deleted

I see a header for the missing cookie but it's not actually received.

The cookie is sent as you can see. Are you using chrome for this?