Channels
#support-questions
- r
rp
03/05/2021, 6:37 AMif you can see which of the two conditions are true (or both may be true), and let me know. - t
thisjust
03/05/2021, 6:40 AMk Ima see what's in that
paramurl - t
thisjust
03/05/2021, 6:47 AMokay so I had the
wrongapiBasePath - t
thisjust
03/05/2021, 6:47 AMI've updated it from
to/auth/.netlify/functions/auth - t
thisjust
03/05/2021, 6:48 AMin both frontend init and backend init - t
thisjust
03/05/2021, 6:48 AMstill having issue though. I'll keep looking - r
rp
03/05/2021, 6:49 AMright. I don't think that would solve it anyway - r
rp
03/05/2021, 6:50 AMCan you do
andconsole.log(url)
on line number 380 (right afterconsole.log(AuthHttpRequest.apiDomain)
)try { - r
rp
03/05/2021, 6:51 AMAlso, you may want do run
andnpm i supertokens-auth-react@0.7.1
. We just updated the repos to fix a bug to do with having anpm i supertokens-node@4.1.1
in the.
.apiBasePath - t
thisjust
03/05/2021, 6:52 AMCopy codevalue of url /.netlify/functions/auth http://localhost:8888 - t
thisjust
03/05/2021, 6:54 AMk, updating those packages - r
rp
03/05/2021, 6:54 AMOkay. Can you print out
on line number 390, just afterconsole.log(err)} catch (err) { - t
thisjust
03/05/2021, 6:59 AMupdating those packages didn't seem to help, and it doesn't seem like that console.log statement isn't printing anything - r
rp
03/05/2021, 6:59 AMokay. So that means that block is not throwing an error either.. - r
rp
03/05/2021, 7:00 AMCan you do
on line number 380, right afterconsole.log( utils_1.normaliseURLDomainOrThrowError(url))try { - r
rp
03/05/2021, 7:00 AMwhat's the value of that? - t
thisjust
03/05/2021, 7:04 AMinteresting - t
thisjust
03/05/2021, 7:04 AMhttps://.netlify - t
thisjust
03/05/2021, 7:04 AMit's changing
intohttphttps - t
thisjust
03/05/2021, 7:04 AMand removing part of the path - r
rp
03/05/2021, 7:04 AMOKay. Got it.. i know what the error is.. will fix it and release the new version - r
rp
03/05/2021, 7:04 AMgive me 30 mins or so.. will push new versions with the fix. - r
rp
03/05/2021, 7:04 AMthanks for your help - t
thisjust
03/05/2021, 7:05 AMYes of course, happy to help! Thanks for your help as well. - r
rp
03/05/2021, 7:05 AMcheers. Will keep you updated. - t
thisjust
03/05/2021, 7:05 AMk - r
rp
03/05/2021, 8:39 AMhey @User please run the following:Copy code
And please try again. This time, things should work as expected.npm i supertokens-website@5.0.10 npm i supertokens-node@4.1.2 npm i supertokens-auth-react@0.7.2 - r
rp
03/05/2021, 9:39 AM@User I have added an example setup with netlify: https://github.com/supertokens/supertokens-auth-react/tree/master/examples/with-netlify - See the frontend configs here: https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-netlify/src/App.tsx#L19 - See the backend config here: https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-netlify/netlify/functions/api.js#L14 - Also I have used "serverless-http" and for making the serverless app work with express. I also needed to use body-parser as seen here: https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-netlify/netlify/functions/api.js#L11 - You can see how session verification (on the backend) works here: https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-netlify/netlify/functions/api.js#L32 - t
thisjust
03/05/2021, 1:52 PMOkay great,
is now working, I was able to extractSession.getJWTPayloadSecurely
from it, and I now have 4 cookies:faunadbTokensIRTFrontendsAccessTokensFrontTokensIDRefreshToken