Nothing has changed, only NPM install

I see. so when you send a query using fetch / axios, do you catch errors from that?

Nope

so that's the issue.

But I also don't make any requests on app load

I actually have no idea how that is occuring

are you sure?

cause the only way this happens is if an API request is being made

Oh wait of course I am

My bad

I'm making requests yup, perhaps it's the change to 2.0 on the back-end

No worries. So you are making an API request to a path that requires an active session. You are getting a session expired error code cause those tokens are not being sent. Check your cookie_domain value

Ah, nice

How do I change the config for supertokens, the config at usr/etc/supertokens is read-only

Change it in the docker start command and restart the container

Oh this isn't being run with docker! 😄 I'm not that far yet, just local dev and I'm doing docker step by step

Docker works but it's too many variables to keep track of rn for myself

ah i see. so use sudo to change the config.yaml file

Ah sure

and then stop and start the supertokens instance

Also, using the new errorHandler() how does one allow this to console.log or add error's to a logger?

you can override the default error handlers for each type of error. In those custom handlers, you can do whatever you want, like logging etc

See https://supertokens.io/docs/nodejs/usage-with-express/custom_error_handling

And I think I've got another error, I managed to make some sort of require cycle

message has been deleted

ah i see. that's an issue with our SDK. Will fix it ASAP. If you can, please raise this issue on github. Things should still work though

ah gotcha, and another thing

SuperTokensRequest.init("https://api.example.com/api/refresh", 440, {});

Is the recommended init for axios

SuperTokensRequest.init("https://api.example.com/api/refresh", 440, true, {});

is the recommended init for fetch axios init shows TS error

ill raise the first on github now

For axios, import from "supertokens-react-native/axios"