603466164219281420 #support-questions

app.use(
  cors({
    origin: "http://localhost:3000",
    allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()],
    credentials: true,
    methods: ["GET", "PUT", "POST", "DELETE", "OPTIONS"],
  }),
)

04/27/2021, 6:43 PM

Yes

user

04/27/2021, 6:43 PM

cool, cool.

user

04/27/2021, 6:43 PM

adding an additional comment about that might be helpful.

user

04/27/2021, 6:43 PM

thanks for clarifying! 🙂

04/27/2021, 6:44 PM

Yea. We will write it in the docs for this 🙂

ZeferiniX

04/27/2021, 11:50 PM

Been wondering, what are the issues if we do not supply the

apiDomain

and/or

websiteDomain

on the

appInfo

? And what is it being used for? https://supertokens.io/docs/nodejs/init

ZeferiniX

04/28/2021, 1:01 AM

are there more details somewhere about the

session_info

table? just wondering if the session handle row for that user's session should be removed if the user signs out

ZeferiniX

04/28/2021, 1:02 AM

or is this used for history purposes that's why it remains here?

04/28/2021, 4:21 AM

> what are the issues if we do not supply the apiDomain and/or websiteDomain on the appInfo? And what is it being used for? On the frontend, the

apiDomain

is used to query your APIs. On the backend, the

websiteDomain

is used to generate password reset / email verification links. The

websiteDomain

is also used on the frontend fro routing purposes in case you have a dedicated sub domain for auth like

auth.example.com

. We plan on writing a page highlighting the significance of all the items in the

appInfo

object since it's quite important.

04/28/2021, 4:23 AM

> are there more details somewhere about the session_info table? The schema of this can be found in Quick Setup > Database section. > just wondering if the session handle row for that user's session should be removed if the user signs out Yes. It should be. The

revokeSession

function does exactly that.

gusfune

04/28/2021, 2:55 PM

Are there any known issues on

{ SignOut }

in NextJS? We seem to have the promise always pending and users are stuck forever with their session :/

gusfune

04/28/2021, 2:55 PM

Forever is way too much, but until it expires.

04/28/2021, 2:56 PM

There are no known issues as such. How are you using signout?

gusfune

04/28/2021, 2:57 PM

import { signOut } from "supertokens-auth-react/recipe/thirdpartyemailpassword"

<button
  onClick={async () => {
    await signOut()
    mutate() //SWR stuff for
    toggle() //closes the menu
    router.push("/") //redirects
  }}
>Logout</button>

04/28/2021, 2:57 PM

Seems right. What's the network tab look like?

04/28/2021, 2:58 PM

What's the response of the signOut API call?

gusfune

04/28/2021, 2:58 PM

Hm, it's stuck loading

http://localhost:3000/api/auth/signout

gusfune

04/28/2021, 2:59 PM

We are using

[[...path]].js

implementation without any customization.

gusfune

04/28/2021, 2:59 PM

And I get in my terminal:

[next] API resolved without sending a response for /api/auth/signout, this may result in stalled requests.

04/28/2021, 3:00 PM

You may want to double check your file: https://supertokens.io/docs/thirdpartyemailpassword/nextjs/setting-up-backend

04/28/2021, 3:01 PM

We had added:

if (!res.writableEnded) {
    res.status(404).send('Not found')
  }

At the ned.

04/28/2021, 3:01 PM

end*

04/28/2021, 3:01 PM

but this would mean that you will get a 404 back. Which means that the sign out API is not being found.. Can I see your backend and frontend config please?