Channels
#support-questions
- t
thisjust
03/05/2021, 6:14 AMDoes this narrow it down to an issue solely with front-end code? - r
rp
03/05/2021, 6:15 AMyes. - r
rp
03/05/2021, 6:15 AMBackend seems to be fine since the right cookies are being set by the API call - r
rp
03/05/2021, 6:15 AMCan you make sure that the supertokens.init call is happening before you run your fetch API on the frontend? - t
thisjust
03/05/2021, 6:17 AMI have an
file, whereAuth.jsx
is run in the outmost scope, whereas the call toSuperTokens.init
occurs inside that file's React componentfetch - r
rp
03/05/2021, 6:17 AMI see. - r
rp
03/05/2021, 6:17 AMIs there any error being printed out in the browser console? - t
thisjust
03/05/2021, 6:19 AMJust what I mentioned above:Uncaught (in promise) Error: No session exists - r
rp
03/05/2021, 6:19 AMhmmm - r
rp
03/05/2021, 6:20 AMand your browser URL is
at the moment?http://localhost:8888 - t
thisjust
03/05/2021, 6:21 AMcorrect - t
thisjust
03/05/2021, 6:22 AMUsing
so ... the web server is served on port 3000, but gets proxied through port 8888 via netlify devnetilfy dev - t
thisjust
03/05/2021, 6:23 AMI don't think that should be an issue, right? - t
thisjust
03/05/2021, 6:24 AMi.e. the /auth API is served directly on port 8888 - t
thisjust
03/05/2021, 6:25 AMand the frontend stuff is proxied from 3000 to 8888 - r
rp
03/05/2021, 6:25 AMCan you go to supertokens-website inside node_modules, and in lib > build > fetch.js > line number 378, do
and in line 398, doconsole.log("line 378")
and then tell me what the output of those are in your console once you call the API?console.log("value of doNotDoInterception", doNotDoInterception) - r
rp
03/05/2021, 6:25 AM> I don't think that should be an issue, right? I don't think that's an issue - t
thisjust
03/05/2021, 6:28 AMokay for that first part, you want it to look like this? - t
thisjust
03/05/2021, 6:28 AMCopy codeif (!AuthHttpRequest.initCalled) { throw Error("init function not called"); console.log("line 378") } - r
rp
03/05/2021, 6:28 AMno. After the IF bracket close - t
thisjust
03/05/2021, 6:28 AMthat's in the same block as the
, just after itthrow - t
thisjust
03/05/2021, 6:29 AMk - t
thisjust
03/05/2021, 6:30 AMand that second part, - t
thisjust
03/05/2021, 6:30 AMCopy code} catch (err) { if (err.message === "Please provide a valid domain name") { // .origin gives the port as well.. doNotDoInterception = utils_1.normaliseURLDomainOrThrowError(window.location.origin) !== AuthHttpRequest.apiDomain && AuthHttpRequest.addedFetchInterceptor; } else { throw err; } console.log("value of doNotDoInterception", doNotDoInterception) } - r
rp
03/05/2021, 6:30 AMafter the closing bracket as well - r
rp
03/05/2021, 6:30 AMThat is just beforeif (!doNotDoInterception) return - t
thisjust
03/05/2021, 6:35 AMCopy codeline 378 value of doNotDoInterception true - r
rp
03/05/2021, 6:35 AMOkay!! So we need to know why
isdoNotDoInterception
.true - t
thisjust
03/05/2021, 6:36 AMHa okay simple! 🙂 - r
rp
03/05/2021, 6:36 AM