You want to render our components only if it's on the client side. To do that, you have to wrap them with the dynamic higher order component from nextjs framework. As shown here: https://supertokens.io/docs/emailpassword/nextjs/setting-up-frontend

If this is already done, then are you using any of our functions from the supertokens-auth-react SDK that's throwing this error?

I mean, can you show me the code that's causing this error? From the screenshot, it's not clear what

originalRenderPage

is.

It is within pages/_document https://nextjs.org/docs/advanced-features/custom-document

Yes. But which function call / component of ours is causing this issue?

Does the basic nextjs + supertokens setup work? Or is that throwing this error?

Just when i try to split them like you mentioned, when the code from docs was implemented everything was working just perfect

I see. So did you wrap the

<SignInUp />

components in the dynamic wrapper?

with ssr: false

No just using the previous code with the new one

Not sure what you mean by previous code.. can you share your code snippet here for how you are using the

SignInUp

component?

Thanks a lot for explanation. it is totally my bad did not pay attention to modification needed for Nextjs. It is working all fine 🙌🏻 🥳

Hello @User I'm using latest supertokens-node version and trying to set up user management API. Why supertokens.getUsersNewestFirst() returns just a subset of users? In dashboard I can click "Export all users as CSV" and get all users and if I try to update user password (EmailPassword.updateEmailOrPassword, **EmailPassword **was imported from supertokens-node/recipe/emailpassword) with id from exported users CSV (which *getUsersNewestFirst * doesn't return) I get *UNKNOWN_USER_ID_ERROR * 🤯

Are you using just email password recipe?

Can you please DM me the email you use for signing into supertokens.io?

@User I'm using thirdpartyemailpassword. Also I've noticed that all new sign ups are added to the list returned by supertokens.getUsersNewestFirst().

Ah I see. So you should not use

EmailPassword.updateEmailOrPassword

. Instead, you should use

ThirdPartyEmailPassword.updateEmailOrPassword

. Also, you can't update the email if someone used social login - since they need to do that on the socail provider's side and relogin to your app for the email to be updated.

There is a limit on the number of users that

getUsersNewestFirst

returns. You need to paginate across them to see all users. If you do this, you should see the same result as you are seeing in the CSV.

switched to ThirdPartyEmailPassword.updateEmailOrPassword, but that doesn't helped with users whose id isn't in getUsersNewestFirst (also there are no nextPaginationToken, so I assume I can see all users in one page) even stranger is next thing, I can sign up with same user email that was exported as CVS from dashboard and then it appear in getUsersNewestFirst. ThirdPartyEmailPassword.updateEmailOrPassword works fine then. I think it may be related to supertokens core upgrade (I'm using managed service, but still) or to users, whose email is unverified

Hmm.. strange. Let me check and get back.

I have DM'd you @User . Please see. Is it possible that you are using the development connectionURI and API key, but downloading the production env CSV?

Is there any way to ask third party provider for more data about user?In my case i would like to get name from facebook login flow.

@User yes. You can get the access token from fb this way: https://supertokens.io/docs/thirdpartyemailpassword/post-login/getting-provider-access-token And then use that to query any info about the user

@rp Thanks! I wonder if its worth to add some configuration about fetching users data from third party providers

lets say https://github.com/supertokens/supertokens-node/blob/48684c37f9f668ddc778452ecc64a9f5d7efdf30/lib/ts/recipe/thirdparty/providers/facebook.ts#L61-L63 can provide it if i pass specific configuration

hmmm. Interesting. So different providers have very different methods of querying for user info. So generically speaking, allowing a user to pass in a custom

params

object may not always work. On the other hand, allowing users to make their own version of

getProfileInfo

would work, but that's the same as just providing the access token and telling users to query (which is possible not anyway). Any other ideas?

Cant configuration be provider specific?

in my case im using only facebook as third party provider

Hmm. We could. But then the return type of

getProfileInfo

would need to become more relaxed. Will need to think about the best way to make this possible - but it certainly would be possible. Could you please open an issue about this on our github?

Let me tinker with it more 👍