After attempting to change all variables to env counterparts

Question

After attempting to change all variables to env counterparts and setting up the system for release I have triggered something that I cannot figure out I have allowed all the necessary headers according to the warnings at some point then I am a loop I feel that there is a session lingering on which I cannot kill

nkshah2 · Answer

After attempting to change all variables to env counterparts and setting up the system for release I have triggered something that I cannot figure out I have allowed all the necessary headers according to the warnings at some point then I am a loop I feel that there is a session lingering on which I cannot kill

nkshah2 · Answer

Hi can you send the config you use when calling SuperTokens init on the frontend and backend Stripping any API keys you may be using

Dhr_RT · Answer

sure

Dhr_RT · Answer

backend

Dhr_RT · Answer

Frontend

nkshah2 · Answer

What are the values set for `BACKEND URL` `FRONTEND URL` `REACT APP BACKEND URL` and `REACT APP FRONTEND URL`

Dhr_RT · Answer

Frontend

Dhr_RT · Answer

Backend

nkshah2 · Answer

And just to make sure your react app does start on PORT 3000 correct

Dhr_RT · Answer

I do have this on my root file on NodeJS

nkshah2 · Answer

You dont need to add the CORS headers manually

nkshah2 · Answer

Can you remove them and try

Dhr_RT · Answer

Sure

nkshah2 · Answer

Just to be clear the part where you do `app use cors ` should stay

Dhr_RT · Answer

yes

Dhr_RT · Answer

Let me set all the variables hard coded instead of env variables

Dhr_RT · Answer

No luck I will flip on debug mode

nkshah2 · Answer

What version of supertokens node are you using

Dhr_RT · Answer

^9 1 2

nkshah2 · Answer

Could you follow this troubleshooting guide and let us know https supertokens com docs thirdpartyemailpassword troubleshooting how to troubleshoot

Dhr_RT · Answer

Nothing here

nkshah2 · Answer

Oh give me a bit

Dhr_RT · Answer

Sure I will be going in transit now I will respond slower

nkshah2 · Answer

Can you post the code where you add the SuperTokens middleware

nkshah2 · Answer

And can you check if `cors` is being added before or after the middleware

nkshah2 · Answer

Were you seeing the same error after switching to local variables or was the error different

Dhr_RT · Answer

same errors

Dhr_RT · Answer

I will change browsers

nkshah2 · Answer

Yep try it with Chrome out of curiosity

Dhr_RT · Answer

Chrome

Dhr_RT · Answer

It almost seems that I need to set the header manually

nkshah2 · Answer

The `cors` middleware should handle that for you Do you see any errors in your API server on startup

nkshah2 · Answer

Can you also try moving your Swagger route after the supertokens middleware and seeing if the behaviour changes

nkshah2 · Answer

I mean this part `app use swaggerUI serve `

Dhr_RT · Answer

I will try in a moment

Dhr_RT · Answer

OK that worked lol

Dhr_RT · Answer

Nice catch

Dhr_RT · Answer

Now I have another issue never encountered before

nkshah2 · Answer

In the backend SuperTokens init you have overridden `signInUpPOST` In that snippet can you log something after calling `originalImplementation signInUpPOST` and check if it gets to that point

Dhr_RT · Answer

sure

Dhr_RT · Answer

Wait I will flush the system

nkshah2 · Answer

Also if you have a default error handler after adding the SuperTokens error handler you can print there and check if you are getting any specific errors

Dhr_RT · Answer

It seems to be working now

Dhr_RT · Answer

I will have to check it out some more

Dhr_RT · Answer

thanks for you help so far

nkshah2 · Answer

Happy to help this thread will be active for the next 24 hours so feel free to ask more questions here