Fair but it fails on me with the cookies

Question

porcellus · Answer

I m happy to help if you can elaborate a bit more

nazzrrg · Answer

Sure I followed the thirdparty auth recipe as a result I have a sAccessToken and a sIdRefreshToken However when I call supertokens doesSessionExist or attemptRefreshingSession they both result in a false value

nazzrrg · Answer

I import supertokens website into html and call the init function prior

porcellus · Answer

but you don t have `sFrontToken` and `sIRTFrontend`

nazzrrg · Answer

```sIRTFrontend``` that one I do value is remove

porcellus · Answer

yeah that s the issue

porcellus · Answer

are you using axios

nazzrrg · Answer

no plain JS

porcellus · Answer

and fetch or XMLHTTPRequest

nazzrrg · Answer

fetch

nazzrrg · Answer

I mean I am somewhat new to js and the init for supertokens is in the file different to the one I am checking for session in but afaik it should not be the issue

porcellus · Answer

it should be fine as long as the init happens before the fetch

porcellus · Answer

an easy way to check is to put console log fetch just before you actually call the fetch

porcellus · Answer

if it says `ƒ fetch native code ` or something like this the init didn t actually go through

nazzrrg · Answer

```if await supertokens doesSessionExist console log 123 ```

nazzrrg · Answer

Thats what comes up false

nazzrrg · Answer

as an example

nazzrrg · Answer

cookies present

porcellus · Answer

oh right can you try logging in again an see what cookies are set

porcellus · Answer

you have all 4

nazzrrg · Answer

I do not have `sFrontToken`

porcellus · Answer

how are you logging in

nazzrrg · Answer

google thirdparty

porcellus · Answer

I meant in your code Do you have a repo I could check out

nazzrrg · Answer

Private as a uni requirement I can send it all here There isn t much

porcellus · Answer

that works for me

nazzrrg · Answer

``` const response = await fetch http localhost 1337 api auth authorisationurl thirdPartyId=google method GET headers rid thirdparty let urlObj = new URL await response json url urlObj searchParams append redirect uri http localhost 1337 auth callback google let url = urlObj toString window location replace url ```

nazzrrg · Answer

step 1 of the guide https supertokens com blog adding social login to your website with supertokens

nazzrrg · Answer

```let code = new URL window location href searchParams get code const response = await fetch http localhost 1337 api auth signinup method POST headers rid thirdparty Content Type application json body JSON stringify code redirectURI http localhost 1337 auth callback google thirdPartyId google window location replace http localhost 1337 page ```step 2

nazzrrg · Answer

that should be an mre

nazzrrg · Answer

removed logs and a request to my api to create own user representation

porcellus · Answer

So then what you should check is if the supertokens init happened before these fetches Like I said an easy way is to log the value of fetch before calling it

porcellus · Answer

I think the fetch in step 2 may be called before the SDK is initialized

nazzrrg · Answer

do I just log the promise I get from fetch to see whats inside

porcellus · Answer

no the fetch function itself

nazzrrg · Answer

Or how exactly do I log fetch

nazzrrg · Answer

ok

porcellus · Answer

`console log fetch ` if it says `ƒ fetch native code ` or something like this the init didn t happen

nazzrrg · Answer

It did not

nazzrrg · Answer

Do I need an extra init on my callback page then

porcellus · Answer

Extra init

nazzrrg · Answer

I mean what exactly happens when I call it Can I simply call it twice

porcellus · Answer

The second init call throws

porcellus · Answer

It should be run exactly once per page reload

nazzrrg · Answer

it will be ok then

nazzrrg · Answer

Yes I do have `sFrontToken` now

nazzrrg · Answer

And the session now exists

nazzrrg · Answer

Thank You

porcellus · Answer

Happy to help