Hello there, Is there any possibility to use localisation/internationalization with i18next inside builtin component provided in recipe[ Only Email and password] Thank you in advance

We don't support internationalisation yet. For now though, you can: 1) Fork the repo and change the language of the text and use your forked version 2) Use JS to find the DOM element and change the text in it dynamically This is something we will work on very soon though.

Finally, you can add this feature to the repo if you like via a PR 🙂

Hi there, I think I have a problem to list all the users. On my supertokens dashboard, I should have 70 users. But If I export all users as csv file I have only 58 user. Same behaviour If I call the

getUserCount()

function with nodejs SDK But when I connect to Postgres Database I can see 66 users (

SELECT * FROM emailpassword_users

).

So what is the correct number of users ?

Hey @mpicciolli is 70 showing for your dev env? Or prod?

Hey @User it's for the dev env

Are you using just email password recipe?

ThirdPartyEmailPassword recipe

Can you tell me the number of rows in thirdparty_users table please?

4 users. Ok it makes sense for the number displayed on the dashboard (66+4 =70)

Hmm. So now the weird part is why the 58 users

yes exactly 😆

Let me investigate and get back by tomorrow. This is strange.

Can you please DM me the email you used to sign up on our site?

For sure. thank you

Thank you too!

GetUserCount returns 70 or 58?

@mpicciolli the issue should be fixed now. Please check.

@User Sounds good ! Thank you so much ! What was the problem ?

hey @User Do you have any suggestion where else i could check whats wrong. I have supertokens core as well as an api in separate containers. versions: supertokens-node@^7.0.2, supertokens-core latest from dockerhub reciper: emailpassword I am stuck on

No Supertokens Core to query.

error on signup and cannot see whats wrong. The logs in supertokens_core do not seem like anything is wrong. I have checked that containers do see each other and can ping each other just normally.

sh
8 Jan 2022 22:35:47:281 +0000 | INFO | pid: 6f16aa35-8966-4fb4-bfb3-6d6e14ff888e | [main] thread | io.supertokens.Main.init(Main.java:213) | Started SuperTokens on 0.0.0.0:3567 with PID: 33

18 Jan 2022 22:35:47:947 +0000 | DEBUG | pid: 6f16aa35-8966-4fb4-bfb3-6d6e14ff888e | [pool-1-thread-1] thread | io.supertokens.cronjobs.CronTask.run(CronTask.java:52) | Cronjob finished: Telemetry

18 Jan 2022 22:36:16:204 +0000 | DEBUG | pid: 6f16aa35-8966-4fb4-bfb3-6d6e14ff888e | [SuperTokens housekeeper] thread | io.supertokens.storage.postgresql.HikariLoggingAppender.doAppend(HikariLoggingAppender.java:136) | SuperTokens - Pool stats (total=10, active=0, idle=10, waiting=0)

After that just keeps logging the same as the last message, pool stats My signup method (it extends the supertokens one):

const signUp =
  (apiInterface: EmailPassword.APIInterface) => async (input: SignUpInput) => {
    if (apiInterface.signUpPOST === undefined) {
      throw Error('SignUpPOST is not reachable.')
    }
    // First we call the original implementation of signUpPOST.
    let response: signUpPOSTResponse = {
      status: 'EMAIL_ALREADY_EXISTS_ERROR',
    }
    try {
      response = await apiInterface.signUpPOST(input)
    } catch (e) {
      console.log('post', JSON.stringify(e))
    }

    // Post sign up response, we check if it was successful
    if (response?.status === 'OK') {
      const { fullName, displayName } = input.formFields.reduce(
        (allFields, field) => ({
          ...allFields,
          [field.id]: field.value,
        }),
        {} as FormUser,
      )
      const { id, email } = response.user
      // Create another entry into meta database
      try {
        // await queryDatabase() ...
      } catch (err: any) {
        console.log(err.stack)
      }
    }
    return response
  }

The error this throws is:

js
Error: No SuperTokens core available to query
    at Querier.<anonymous> (/home/node/app/node_modules/supertokens-node/lib/build/querier.js:225:27)
    at Generator.next (<anonymous>)
    at /home/node/app/node_modules/supertokens-node/lib/build/querier.js:30:75
    at new Promise (<anonymous>)
    at __awaiter (/home/node/app/node_modules/supertokens-node/lib/build/querier.js:12:16)
    at Querier.sendRequestHelper (/home/node/app/node_modules/supertokens-node/lib/build/querier.js:218:13)
    at Querier.<anonymous> (/home/node/app/node_modules/supertokens-node/lib/build/querier.js:244:43)
    at Generator.throw (<anonymous>)
    at rejected (/home/node/app/node_modules/supertokens-node/lib/build/querier.js:22:44)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

any help / direction would be appreciated

There was an issue with migration we had done 😦 won’t happen again

Hey! What connectionURI have you passed to the init function call?

Is there an example of this https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/get-user-info#on-the-frontend, but for Nextjs?

getting errors on the build stage for some reason when using this implementation.

Did you get an error after following the steps for "Without React Context"? Also could you send the error?

here is the error

rror: SuperTokens must be initialized before calling this method.
If you are trying to use this method doing server-side-rendering, please make sure you move this method inside a componentDidMount method or useEffect hook.

haven't tried without versino yet

react without context seems to work

I'm assuming you can't create a context in app since we also call the init function there