Hello - I'm using the passwordHashesImport api to import users from Auth0, but would there be a way to set "isVerified" to true during that process?

I am using this in config config: { thirdPartyId: 'google', clients: [ { clientId: process.env.GOOGLE_CLIENT_ID, clientSecret: process.env.GOOGLE_CLIENT_SECRET, clientType: 'web' }, { clientId: process.env.IOS_GOOGLE_CLIENT_ID, clientType:'ios' }, { clientId: process.env.ANDROID_GOOGLE_CLIENT_ID, clientType:'android' } ], }, but getting this error Error: please provide exactly one client config or pass clientType or tenantId

Good morning, I've added recently email verification to my app. However now one the user first loads the page, the verify call takes like 6 seconds, also it calls the verify email api 2. Im pretty sure im doing something incorrectly 😅

Hey there, How could I understand what is the error? What I know is that when editing the metadata, the error happens

Why am I getting this axios error when sending request to the api. Just to clear things off, I have not protected this api route or sending this 401 status from my api route.

Hi there. Thank you to all the developers /maintainers of supertokens! I've been loving the development experience so far. I have been having a weird issue I was hoping I could get some help with. On initial login locally I am always getting a refresh token through the third party login flow (right now I am using google). When i deployed my app to AWS, I now only get a refresh token on the initial login flow, but not on subsequent logins. I would guess this is something on the google side, but I was wondering if this is something others have experiences or have some familiarity with.

I tried to run the vue router example in the docs, but I couldn't get it to work with:

path: "/auth*",

. By reading https://router.vuejs.org/guide/migration/#Removed-star-or-catch-all-routes, it seems that catch-all routes handling changed. I managed to get it to work with

path: "/auth:pathMatch(.*)*"

. Is this the correct way to do it?

I'm using the managed SuperTokens service, how do I go about updating the version of core it uses, think we are on 4.2 at the moment and would like to go to the latest version in the dev environment

is it possible to prevent ST from adding Authorization: Bearer TOKEN ? 🙂 We're using header-based auth, but we also have basic auth on out test sites, to prevent outsiders from snooping around 😛 We're already adding the token to a custom header

Helo, suddenly the supertokens that I deployed to my fly.io throw an error from backend

2023-05-27T06:06:15.831 app[148ed5d7a72e68] sin [info] {"level":50,"time":1685167575831,"pid":529,"hostname":"148ed5d7a72e68","reqId":"req-7k","err":{"type":"Error","message":"SuperTokens core threw an error for a POST request to path: '/recipe/session' with status code: 500 and message: Internal Error\n","stack":"Error: SuperTokens core threw an error for a POST request to path: '/recipe/session' with status code: 500 and message: Internal Error\n\n at Querier.<anonymous> (/app/node_modules/supertokens-node/lib/build/querier.js:252:31)\n at Generator.throw (<anonymous>)\n at rejected (/app/node_modules/supertokens-node/lib/build/querier.js:22:44)\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)"},"msg":"SuperTokens core threw an error for a POST request to path: '/recipe/session' with status code: 500 and message: Internal Error\n"}

2023-05-27T06:06:15.832 app[148ed5d7a72e68] sin [info] {"level":30,"time":16

and from supertokens-core