603466164219281420 #support-questions

So the error is complaining about SuperTokens.init not being called, if you followed the steps on this page https://supertokens.io/docs/thirdpartyemailpassword/nextjs/init#6-call-the-frontend-init-functions the init function only gets called on the frontend (window is not undefined). Maybe you tried using the session context without making the same check?

pogseal

01/19/2022, 7:17 AM

yea i have it setup like that

pogseal

01/19/2022, 7:19 AM

will try moving out of app.tsx

nkshah2

01/19/2022, 7:21 AM

Just to rule it out, you have wrapped your component with

ThirdPartyEmailPasswordAuth

pogseal

01/19/2022, 7:22 AM

yup. It actually works fine when it's not wrapped

nkshah2

01/19/2022, 7:23 AM

Interesting, we will investigate this. Can you open an issue in supertokens-auth-react for this? Makes it easier to track

pogseal

01/19/2022, 7:23 AM

Will mess around with it a bit more, perhaps I set it up wrong. Will create an issue if I don't make any progress

nkshah2

01/19/2022, 7:24 AM

Alright, thanks!

nkshah2

01/19/2022, 7:52 AM

@User getServerSideProps may be a better way to achieve what you want: https://supertokens.io/docs/thirdpartyemailpassword/nextjs/session-verification/in-ssr#1-we-use-getsession-in-getserversideprops

nkshah2

01/19/2022, 7:58 AM

Also if you wrap your component in the way described on this page https://supertokens.io/docs/thirdpartyemailpassword/nextjs/protecting-route, you should be able to use React context without any issues

pogseal

01/19/2022, 8:00 AM

Would this help in getting the user id? I don't want to protect a page, just want read the user data.

nkshah2

01/19/2022, 8:03 AM

You can use the

requireAuth

prop to allow access to the page without requiring a session

pogseal

01/19/2022, 8:08 AM

got it, will have a look

pogseal

01/19/2022, 8:33 AM

Copy code

Server Error
TypeError: Cannot read property 'wrapperUsed' of undefined

This error happened while generating the page. Any console logs will be displayed in the terminal window.
Source
pages/_app.tsx (88:20) @ Function.MyApp.getInitialProps

  86 | try {
  87 |   // getSession will do session verification for us
> 88 |   session = await Session.getSession(context.req, context.res);
     |                  ^
  89 | } catch (err) {
  90 |   if (err.type === Session.Error.TRY_REFRESH_TOKEN) {
  91 |     // in this case, the session is still valid, only the access token has expired.

pogseal

01/19/2022, 8:33 AM

getting this error when setting it up

nkshah2

01/19/2022, 9:11 AM

Did you get a chance to try the protected route setup?

nkshah2

01/19/2022, 9:18 AM

This should be in getServerSideProps and not getInitialProps

agnieszka.olszewska

01/19/2022, 1:46 PM

Hi all, I have just upgraded

supertokens-auth-react

lib to 0.18 version and I keep getting node error in my terminal:

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

. It works correctly with version 0.14.x. Any higher version produces the above error. I use node

v14.16.1

. Did anyone have a similar issue?

01/19/2022, 1:54 PM

Hi @agnieszka.olszewska can you please tell us what code causes that?

01/19/2022, 1:54 PM

Perhaps it would be best to open an issue about this on our GitHub

agnieszka.olszewska

01/19/2022, 1:55 PM

I'm not really sure which part of the code. Just hoped someone have already run into the same issue. I will further investigate to check what causes it and get back to you as soon as I have any further info

01/19/2022, 2:07 PM

Ok thank you!

M̸̹̣i̼̗č̹̰o̧̲ͅ

01/19/2022, 7:52 PM

http://0.0.0.0:3567 and http://localhost:3567 both throw this error

M̸̹̣i̼̗č̹̰o̧̲ͅ

01/19/2022, 8:08 PM

i also see http://localhost:3567/hello the Hello page

agnieszka.olszewska

01/19/2022, 8:12 PM

Hi again, the problem occurs when I try to import anything from the

emailpassword

receip, for example

import { EmailPasswordAuth } from 'supertokens-auth-react/recipe/emailpassword'

. When I only use

session

receip, everything works well.

01/20/2022, 3:13 AM

@M̸̹̣i̼̗č̹̰o̧̲ͅ are you running the node process in a docker container?

01/20/2022, 3:17 AM

@agnieszka.olszewska try this maybe? https://stackoverflow.com/questions/55613789/how-to-fix-fatal-error-ineffective-mark-compacts-near-heap-limit-allocation-fa?rq=1

M̸̹̣i̼̗č̹̰o̧̲ͅ

01/20/2022, 8:14 AM

I am yes

01/20/2022, 8:18 AM

I see. So localhost in there refers to inside the container itself. You need to use the local network IP instead.

agnieszka.olszewska

01/20/2022, 12:52 PM

I have actually tried it, but still I think there might be some problem. My node process takes about 600MB of memory and once I add the import statement

import { EmailPasswordAuth } from 'supertokens-auth-react/recipe/emailpassword'

, it increases up to 2GB...