I m thinking it could have something to do with express 4 To

Question

I m thinking it could have something to do with express 4 To set headers in express 4 res set key value But looking at this it seems it tries setting the header with methods res header and res setHeader https github com supertokens supertokens node blob master lib ts framework utils ts

rp · Answer

Hey < hoffeman> this usually happens if you pass in the request object instead of passing in the response object in some function of ours which requires them as the input

rp · Answer

it can also happen if you have already sent the response and then you trigger something that causes a header update from our side

hoffeman · Answer

yes it is weird since it only happens sometimes Im thinking it could be when the client is using the refresh token

rp · Answer

probably not unless you have overriden the refresh API

rp · Answer

it s most like that the response has already been sent

hoffeman · Answer

true

hoffeman · Answer

im also using the SupertokensExceptionFilter from the guide so it should stop propagation if headers have been sent

rp · Answer

yeaa maybe you can see which function call is causing this error

hoffeman · Answer

Nest 78 07 05 2022 9 56 51 AM ERROR ExceptionsHandler Error while setting header with key front token and value eyJ1aWQiOiJkYjZmYWVlNC0zNDU1LTRlYTYtODdjOS04N2M2NjA4MzA0YWYiLCJhdGUiOjE2NTcwMTg2MTExNTEsInVwIjp7InJvbGUiOiJBRE1JTiIsIm9yZ2FuaXphdGlvbklkIjoidGVzdCJ9fQ== rapid api 1 | Error Error while setting header with key front token and value eyJ1aWQiOiJkYjZmYWVlNC0zNDU1LTRlYTYtODdjOS04N2M2NjA4MzA0YWYiLCJhdGUiOjE2NTcwMTg2MTExNTEsInVwIjp7InJvbGUiOiJBRE1JTiIsIm9yZ2FuaXphdGlvbklkIjoidGVzdCJ9fQ== rapid api 1 | at Object setHeaderForExpressLikeResponse usr src app node modules supertokens node lib build framework utils js 236 15 rapid api 1 | at ExpressResponse setHeader usr src app node modules supertokens node lib build framework express framework js 111 21 rapid api 1 | at Object setFrontTokenInHeaders usr src app node modules supertokens node lib build recipe session cookieAndHeaders js 73 9 rapid api 1 | at Object usr src app node modules supertokens node lib build recipe session recipeImplementation js 216 44 rapid api 1 | at Generator next rapid api 1 | at fulfilled usr src app node modules supertokens node lib build recipe session recipeImplementation js 15 36 rapid api 1 | at processTicksAndRejections node internal process task queues 95 5

hoffeman · Answer

this is the only stack trace i get

hoffeman · Answer

i also tried disabling all exceptionfilters

rp · Answer

Can you upload your code and share it on github

hoffeman · Answer

it seems to only happen after i while so im thinking it has something to do when it needs to refresh the token

hoffeman · Answer

yea sure can I invite you it is a private repo

rp · Answer

deos this happen when calling the refresh API only

rp · Answer

yea Invite me to id

rp · Answer

rishabhpoddar is my github

hoffeman · Answer

no it is actually a regular api request

rp · Answer

< porcellus> can help here too

hoffeman · Answer

i have added you to the repo now

rp · Answer

ok thanks

hoffeman · Answer

ignore all the commit messages plz

rp · Answer

haha

rp · Answer

fair

hoffeman · Answer

cloud api api common auth

hoffeman · Answer

thats where the supertoken module is located

rp · Answer

ok thanks

porcellus · Answer

hi

porcellus · Answer

so what I d check is the kind of error that s caught and rethrown as the error while setting header

porcellus · Answer

are you running this locally

hoffeman · Answer

yes

hoffeman · Answer

let me check

hoffeman · Answer

hmm do you have an idea how to check the kind of error in nest

hoffeman · Answer

tried using a catch all but cant the error type

porcellus · Answer

oh I think the easiest way is to just edit `node modules supertokens node lib build framework utils js 236 15`

hoffeman · Answer

TypeError res getHeaders is not a function

hoffeman · Answer

thats what i initially though express 4 uses res set key value for headers

hoffeman · Answer

could be that

hoffeman · Answer

oh or sorry

hoffeman · Answer

its the getHeaders

hoffeman · Answer

but that should be get in express 4

porcellus · Answer

yep

rp · Answer

we wrap the res object in supertokens to standardise the functions across different frameworks In our wrapper we have `getHeaders` as a function

hoffeman · Answer

ah ok any idea how i can continue troubleshooting

rp · Answer

let us check

rp · Answer

< kakashi 44> see here please

rp · Answer

< hoffeman> can you please open an issue about this on our github

rp · Answer

we will fix it right away

hoffeman · Answer

sure

rp · Answer

thanks

hoffeman · Answer

if i relogin on the frontend it works again it is only after being idle and then making a request this happens

hoffeman · Answer

any special guidelines i need to follow for the issue

rp · Answer

Not really you can just describe it however you like

rp · Answer

In the JS code you modified can you print out the value of `res` What does it print

hoffeman · Answer

i just reloggedin probably have to wait a while before the error occurs again

hoffeman · Answer

but ill post here asap

rp · Answer

right Can you delete the access token from cookies and then make an API request

hoffeman · Answer

y

rp · Answer

Maybe that will trigger the error

hoffeman · Answer

nope got a more stuructured error Access token has expired

hoffeman · Answer

now i got it

hoffeman · Answer

not exactly the same though

rp · Answer

ok Great Can you show me what the value of `res` is

hoffeman · Answer

there is almost the full res object

hoffeman · Answer

the console truncated the first part

hoffeman · Answer

if needed i could try to save it as a file

rp · Answer

right I am seeing it now

rp · Answer

Can you show the full object please

hoffeman · Answer

ill try i think i get a circular json error when JSON stringiy the object

rp · Answer

Can you try and log ``` console log res getHeaders console log res get ```

hoffeman · Answer

sure but note that the error i get now after deleting the cookie is not happening in the same function

hoffeman · Answer

but it could probably be related

rp · Answer

right

hoffeman · Answer

undefined Function header

hoffeman · Answer

so getHeader and getHeaders is undefined

hoffeman · Answer

res get is a function

rp · Answer

ok thanks This is helpful

hoffeman · Answer

i opened a issue btw https github com supertokens supertokens node issues 346

rp · Answer

thank you

rp · Answer

Hey < hoffeman> how can I run the server on my local machine

hoffeman · Answer

Hi sorry for late response Just run npm run dev Requires docker and docker compose though

hoffeman · Answer

You might also need a dev account json in root dir I think it will start with a dummy

rp · Answer

Ok thanks

rp · Answer

hey < hoffeman> i tried to setup a new nestjs project similar to yours and it all works fine Can we get on a call to debug this on your project

rp · Answer

You can pick a time here https supertokens com call user

hoffeman · Answer

Yes i booked a time on friday Did you succeed to start my project or a new scaffold nestjs

rp · Answer

Hey I couldn t get the project you gave us to work that s why i asked for a call so we can debug it

nkshah2 · Answer

Hey < hoffeman> Just let us know when you re ready for the call

hoffeman · Answer

yes

hoffeman · Answer

ok i think i can show you now

rp · Answer

cool

hoffeman · Answer

should we use the old meeting room

rp · Answer

https us06web zoom us j 89653114673 pwd=RHoyN1U4YjBSQUMvWkxJTy9IWmRPUT09