Hi there, i think this is a dumb qn or i must have overlook smtg but im desperate after trying to fix this for the last 3 weeks. Im not sure am I facing a small problem with configuration or not but my CORS policy error has been quite persistent. Im using custom own UI documentation to set up supertoken in the app however this problem keep persist. 1. im unsure about my basepath as i dont know should i specify

/auth

or not in the apiBasePath during init phase or does Supertokens already has

/auth/signin

to be setup and thus do not need my specification of

/auth

part. 2. my website domain is also another issue. my website domain is localhost:3000 like any other testing domain however it by itself does not have the app as the app directory is under

/app

so should i specify my websiteBasePath to be that ? but regardless of both with or without, it still has CORS issue. 3. I checked my backend, and had Postman + curl test, all is working fine howver when it comes to frontend it does not. Background: Initial approach: im working with Flask + React/Redux-observables implementation. I wanted to just implement authentication feature, so I thought of using normal Axios fetch a self made BE API then use backend Flask

signin

function from Supertoken emailpassword recipe will be fine (basically no supertoken calls in frontend other than the init function in global level. however without the frontend sdk calling

signIn

in my React component, it does not seem like the created session cookies are being managed thus I need to set up Frontend and ditch the whole Axios approach. So the CORS policy error keep arising when I want to directly call

signin

in my React component, may I know if BE has no issue, which leads to only FE issue, what exactly might be the problem? isit the configuration? tq in advance