hey @User , did you set cors correctly on your backend?

can i see the code for that?

sure

your origin in cors has to be

http://localhost:3000

and not just

localhost:3000

The previous issue was solved, thanks!

But now when I try to signup, it throws another error

which is?

same error goes for the post route as well

you need to enter the API key along with the connection URI as seen here: https://supertokens.io/docs/thirdpartyemailpassword/quick-setup/core/saas-setup#connecting-the-backend-sdk-with-supertokens-

Works Perfectly now

Thanks a ton @User !

the backend setup docs dont have the apiKey in them

ok great! Just out of curiosity, when you copied the connectionURI, did you miss out on the API key part in the popup?

> the backend setup docs dont have the apiKey in them Cause that is optional.

I didnt actually, I wondered if we have an api key then why arent we adding it

I see

> I didnt actually, I wondered if we have an api key then why arent we adding it Ahh.. fair enough.

Thanks

It would be great if you could add an optional section in the docs, for people who are not setting up a self hosted server

Thanks! Will consider.

Thanks for the guidance 😄

Can I pass the private key for Apple like that or does it have to be the content of the key as string?

It has to be the content of the key as a string

Question: I wrap my React project with Capacitor so I can deploy native apps to the App Stores. When you open the app, it basically opens a "localhost" webview On iOS its: ``capacitor://localhost`` on Android its: ``http://localhost`` However on the SuperTokens backend I can only specify a single string for "websiteDomain". How can I solve this?

I think I need to setup deep links:

@User so the website domain value is for things like generating the password reset links or to send an email verification link. Would you want those links to be

http://localhost/...

? If yes, then you should set the value of that as

http://localhost

So there is no response from that? That explains it.. Perhaps your Nginx config is blocking OPTIONS APIs? One way to test this is to remove Nginx from your setup and try to get it to work.

possibly

I get this in

systemctl status nginx