Anyone get errors with token refreshes?

Hi, I am struggling to get the dashboard working. I have followed the documentation correctly and I am initing the dashboard in the recipe, however I just get to a not found when browsing to /auth/dashboard. I had this working once before be now when I have revisited this I just get this issue now.

sh
Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  TCPWRAP

      13 |  */
      14 | function setup(app: Express) : any {
    > 15 |     SuperTokens.init({

when I'm testing my nodejs app its showing up with this error how can I fix this

Hi! I am running into a problem on the backend... My sessions are getting created just fine, and I can use them on the frontend without any problems. However, when I try to use the verifySession() middleware in the backend, it is returning

session = undefined

. I suspect that it is a configuration issue. I am using Firebase Functions, and this is a different function (so a different route / endpoint). Still, I have not been able to successfully configure... Any thoughts?

Hey, I've been hit with "`Access to fetch at 'https://[backend-url]/auth/signin' from origin 'https://[frontend-url]' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled`" and I can't really seem to solve it. I'm able to sign up users but not login.

Since SuperTokens does not offer a C# SDK, then how can I implement a social login from scratch using C# (Xamarin)? It is not obvious in the documentation. What I am hoping for is a series of API calls and/or website URLs to show in a web browser control instead of SDK calls because SuperTokens does not provide an SDK for this language

I'm having this TypeScript problem when setting up the auth UI in a Next.js app:

users:build: info  - Linting and checking validity of types...
users:build: Failed to compile.
users:build: 
users:build: ./pages/auth/[[...path]].tsx:21:6
users:build: Type error: 'SuperTokensComponentNoSSR' cannot be used as a JSX component.
users:build:   Its element type 'ReactElement<any, any> | Component<unknown, any, any>' is not a valid JSX element.
users:build:     Type 'Component<unknown, any, any>' is not assignable to type 'Element | ElementClass'.
users:build:       Type 'Component<unknown, any, any>' is not assignable to type 'ElementClass'.
users:build:         The types returned by 'render()' are incompatible between these types.
users:build:           Type 'React.ReactNode' is not assignable to type 'import("/Users/james/Code/oughtinc/elicit-mono/apps/users/node_modules/@types/react/index").ReactNode'.
users:build:             Type '{}' is not assignable to type 'ReactNode'.
users:build: 
users:build:   19 | 
users:build:   20 |   return (
users:build: > 21 |     <SuperTokensComponentNoSSR />
users:build:      |      ^
users:build:   22 |   )
users:build:   23 | }

This is when using the Auth component directly from https://supertokens.com/docs/thirdpartypasswordless/nextjs/setting-up-frontend

Hi everyone, I am trying to input first_name and last_name as part of emailpassword signup. I tried adding a first_name and last_name InputFormField and ran a simple curl to post a signup with those values but I dont think they are coming through. If I view the user management dashboard I see "FEATURE_NOT_ENABLED" for both first name and last name. I get the feeling that this is not the right way to set it? Anyone has any idea what I may have done wrongly?

I have supertokens-frontend running on localhost:3000 and different project for backend on localhost:3002 from UI when I am trying to login to google, I get "recipeImplementation.js:163 GET http://localhost:3002/auth/authorisationurl?thirdPartyId=google 404 (Not Found)" but localhost:3002 is up

I'm using Nestjs as backend, with both rest and graphql implementation. How should I set the token in graphql playground?