Trying to make a request to my backend but getting back unauthorized. I understand cookies are sent automatically? I previously successfully received the cookies in the response headers of

signup/code/consume

. Also using

'Access-Control-Allow-Credentials': true

on my request to the backend. What am I missing? After receiving the cookies from

signup/code/consume

I should see the cookies on dev tools>storage>cookies, correct? because I don't. Btw, I'm using

fetch

, not

axios

Trying to make a request to my backend but getting back unauthorized. I understand cookies are sent automatically? I previously successfully received the cookies in the response headers of

signup/code/consume

. Also using

'Access-Control-Allow-Credentials': true

on my request to the backend. What am I missing? After receiving the cookies from

signup/code/consume

I should see the cookies on dev tools>storage>cookies, correct? because I don't. Btw, I'm using

fetch

, not

axios

I'm querying from my frontend at

https://localhost:3000/

my backend (FastAPI) at

https://acheron-api.herokuapp.com/

Https? And not http?

both https... I'm not doing anything to appInfo on the frontend

So on the frontend, what’s your apiDomain value?

those are fine, if I take out the validation at the backend api I get the resposne

Are you calling supertokens.init before using

fetch

? Are you using

node-fetch

or the browser's inbuilt fetch?

yes, and no. it's sveltekit's fetch.. but just normal fetch for this matter

I mean, are you importing fetch from somewhere and using that?

I'm not importing fetch.. I'm using the default one on a .js file

Hmmm

now not sure what I did but I'm no longer getting the sign response, recognize the reason for this error?

That’s probably an error in how you are sending email / sms. The callback function you implemented is throwing that error

yea I think I have it, 1 sec, rebuilding

Ok. This seems fine

now it's working, had a retard 'await' while requesting the email in the backend. See? I'm getting the cookies

So two things: - The cookies are attached to the api domain, but you are viewing the website domain's cookie store. - Im sure that the interceeptors are not being applied to

fetch

and thats' why things are not working

ignore the 'token' there

In the

.then

of fetch, can you call

await supertokens.doesSessionExist()

?

I can't use it there, it says SuperTokens is undefined. that's a

api.js

utility

Right. Are you calling supertokens.init on the frontend?

yes.. I'm calling it on the layout file for all routes

So this fetch, is it called on server side or client side?

client side, on mount

Cause if it’s the client side, you can import supertokens from supertokens-website and call that function in the .then

SuperTokens is init'd client side, on mount

Right. So you should be able to call supertokens.doesSessionExist in the .then of the fetch?

it's returning false

Are you sure that supertoeks.init is being called before calling fetch?

yes I even tried to initing right before the fetch

Yeaaaa. Fair. Can you please book a slot using the link on our site

yes, but damn the soonest is tmrw at 2pm

Well. Yeaaa.

will take that one, thanks 😄

Oh wow.