not sure how I will be able to help here. The issue seems to come from the way you have setup your build env.

Nooo what steps should I take??

try cleaning your project and rebuilding, make sure the bundle being sent to the app is not an older version

There’s no mention of supertokens in the repo afaik

Ok

yea so the only way those headers are being added is cause somehow, your app is loading the older bundle version

Bundle.is!

Bundle.js!!

huh?

mainBundle.js might be old?

i have no idea haha.. depends on your setup

Ok I’ll try to figure it out and report back! Thanks

cool!

Hey @rp where are those interecptors located in the bundle so I can see where they are, if they are still there and how to remove them?

for example Are they in the IOS folder, the android folder, what area

I did a fuzzy search for header

xsrfCookieHeader

and it came back with no results

they will be in the same place where ur JS code is located.

yeah but those headers are even working with fetch

I used fetch api for requests and still had these headers and network error

So it's going to be a little difficult for me to help you over text like this. Becasue the issue is not necessarily to do with SuperTokens here. It's a very strange occurrence.

xsrfCookieHeader

is not something we add either

@rp does supertokens set any of these, this is a new screenshot after removing everything

none of them

Ah, damn so im on my own 😦

haha i guess

I'm sure you will fix it haha!

Just a general question

Does SuperToken handle email verifications

Like if I register does it send me a unique link where I can verify my registration

hey @User we are building that feature out. There will be two ways we provide email verification (and you can choose between them): 1) When a user signs up, they get asked to verify their email. Only post that will their sign up succeed 2) A user can sign up with an unverified email, start to use the service, and we display a (customisable) bar on pages reminding them to verify their email. You can also choose to prevent them from using certain features unless they verify their email. Which one do you prefer?