Think I might have a bug report regarding user meta the dash

Question

Think I might have a bug report regarding user meta the dashboard I m using ThirdPartyEmailPassword receipie in my FE and BE configs And UserMeta Dashboard in my BE config When I go to the dashboard to edit a users name and click save I get these logs ``` Error Initialisation not done Did you forget to call the SuperTokens init function at Function getInstanceOrThrowError app node modules supertokens node lib build recipe emailpassword recipe js 199 15 at app node modules supertokens node lib build recipe dashboard api userdetails userPut js 76 18 at Generator next at app node modules supertokens node lib build recipe dashboard api userdetails userPut js 30 75 at new Promise ``` But when I refresh the dashboard the meta has actually saved

oldhack · Answer

This is what my nextjs auth handler looks like ``` supertokens init backendConfig export default async function superTokens req NextApiRequest Request res NextApiResponse Response NOTE We need CORS only if we are querying the APIs from a different origin await NextCors req res methods GET HEAD PUT PATCH POST DELETE origin process env NEXT PUBLIC APP DOMAIN credentials true allowedHeaders content type supertokens getAllCORSHeaders await superTokensNextWrapper async next => This is needed for production deployments with Vercel res setHeader Cache Control no cache no store max age=0 must revalidate await middleware req res next req res if res writableEnded res status 404 send Not found ```

oldhack · Answer

Ah also super interesting is that I can edit the user meta in the meta box successfully and it works The PUT request to user fails with a 500 but the PUT request to meta is good definitely sounds like a bug

rp · Answer

< nkshah2> can help here

nkshah2 · Answer

We released a fix for this today could you try clearing browser cookies and trying again

nkshah2 · Answer

Or just hard refresh the dashboard to force the browser to fetch it again

oldhack · Answer

Oh sorry this is self hosted

nkshah2 · Answer

That shouldn t be a problem try clearing cache for the dashboard url and refreshing

oldhack · Answer

But my code won t change I just experienced the issue a moment ago

nkshah2 · Answer

The dashboard is fetched from a cdn which we updated recently the backend fetches the latest patch version so force reloading should fetch the latest version that is supported by your backend sdk

oldhack · Answer

Issue remains

nkshah2 · Answer

Can I see the recipe list you are providing when calling SuperTokens init on the backend

oldhack · Answer

``` const recipeList = ThirdPartyEmailPassword init EmailVerificationNode init mode REQUIRED SessionNode init jwt enable true UserMetadata init if process env NEXT SUPERTOKENS DASHBOARD KEY console log adding supertokens dashboard recipe recipeList push Dashboard init apiKey process env NEXT SUPERTOKENS DASHBOARD KEY else console log skipping supertokens dashboard ```

nkshah2 · Answer

Can you send the payload for the api that is failing From the network tab

oldhack · Answer

``` recipeId emailpassword userId e7c863b4 ce35 4b20 924f d34926f9cd72 phone email gmail com firstName Foob lastName Bam ```

nkshah2 · Answer

Are you seeing any other logs when your server starts up

oldhack · Answer

No only the one I posted above whenever I try to make the request ``` Error Initialisation not done Did you forget to call the SuperTokens init function at Function getInstanceOrThrowError app node modules supertokens node lib build recipe emailpassword recipe js 199 15 at app node modules supertokens node lib build recipe dashboard api userdetails userPut js 76 18 at Generator next at app node modules supertokens node lib build recipe dashboard api userdetails userPut js 30 75 at new Promise ```

nkshah2 · Answer

Right can you make an issue for this in SuperTokens node I ll take a look at it in a bit

oldhack · Answer

I think I found the bug https github com supertokens supertokens node blob master lib ts recipe dashboard api userdetails userPut ts L4

nkshah2 · Answer

Yep that s right we ll be rolling out a fix soon

rp · Answer

hey < oldhack> this bug has been fixed now in our latest version of the node SDK Version 12 1 1