603466164219281420 #general

Docs

Join the conversation Join Discord

Channels

community

welcome-andrew-rodriguez

welcome-ankit-choudhary

welcome-anthony-stod-custodio

welcome-call-in

welcome-chwalbox

welcome-claybiokiller

welcome-foxbarrington

welcome-himanshu-kukreja

welcome-hossambarakat

welcome-ichikawakazuto

welcome-jonas-alexanderson

welcome-pavan-kumar-reddy-n

welcome-pineappaul

welcome-poothebear

welcome-rick

welcome-samuel-qosenergy

welcome-samuelstroschein

welcome-shubhamgoel23

welcome-shubhamkaushal

welcome-vikram_shadow

welcome-yann

Channels

general

12/19/2021, 11:16 AM

@User you can check if a user is signed it or not like this: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/sessions/checking-session-front-end. If they are signed in, then you show the sign out button, else not

12/19/2021, 4:39 PM

@User qr code login like telegram?

12/19/2021, 6:07 PM

@aV we will add some version of it eventually. Just not sure when

12/19/2021, 6:16 PM

@User I've tried https://supertokens.io/docs/thirdparty/common-customizations/sessions/checking-session-front-end

12/19/2021, 6:17 PM

And it gives me an error, "Supertokens must be initialized first" or something

12/19/2021, 6:17 PM

Right. Have you called the supertokens.init function? If yes, where do you call it? It should be one of the first things that happen on app load.

12/19/2021, 6:18 PM

before rendering the

ThirdPartyAuth

component

12/19/2021, 6:18 PM

I'm using thirdpartyauth in my index.js file

12/19/2021, 6:18 PM

should it happen in there?

12/19/2021, 6:18 PM

you can, as long as you are sure to call the supertokens.init function before the

render

function is called.

12/19/2021, 6:19 PM

OKay, would _app.js be a better place to call it?

12/19/2021, 6:19 PM

Just wondering

12/19/2021, 6:19 PM

the init function? Yea..

12/19/2021, 6:19 PM

I already have

supertokensNode.init(backendConfig())

12/19/2021, 6:19 PM

in there

12/19/2021, 6:20 PM

thats the backend config. You need to call the frontend init as well. See this step: https://supertokens.io/docs/thirdparty/nextjs/init#6-call-the-init-functions

12/19/2021, 6:20 PM

if (typeof window !== 'undefined') {
  SuperTokensReact.init(frontendConfig())
} else {
  initNode().catch(console.error)
}

12/19/2021, 6:20 PM

this code is already in there

12/19/2021, 6:20 PM

In `_app.js`:

import SuperTokensReact from 'supertokens-auth-react'

if (typeof window !== 'undefined') {
  SuperTokensReact.init(frontendConfig())
}

12/19/2021, 6:20 PM

oh..

12/19/2021, 6:21 PM

Yea not sure whats happening

12/19/2021, 6:21 PM

Can I see the stack trace of the error?

12/19/2021, 6:22 PM

sure

12/19/2021, 6:22 PM

ah i see. you must be using

ThirdPartyAuth

in server side rendering.. which will not work

12/19/2021, 6:23 PM

See this: https://supertokens.io/docs/thirdparty/nextjs/protecting-route

12/19/2021, 6:23 PM

You need to wrap the call to

ThirdPartyAuth

with:

dynamic(
  new Promise((res) =>
    res(ThirdParty.ThirdPartyAuth)
  ),
  { ssr: false }
)

12/19/2021, 6:25 PM

So then you can do:

<ThirdPartyAuthNoSSR requireAuth={false}>
  <ProtectedPage />
</ThirdPartyAuthNoSSR>

12/19/2021, 6:26 PM

ok thanks

12/19/2021, 6:26 PM

so i believe i tried that, but what i'm trying to do is not render a signout button

12/19/2021, 6:26 PM

and this approach redirects me to login