SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

SuperTokens.com

Currently trying to override the callback theme using `supertokens-auth-react@0.30.2`, using the new `ThirdpartyEmailPasswordComponentsOverrideProvider` and overriding the component `ThirdPartySignInAndUpCallbackTheme_Override`. It's the only component that I've tried that I just can't get to work. Wondering if this is an issue with this version or if it's something local to me.

<@435107855880683521> can help here - when he is available

Thanks! I appreciate the time. Is there any other info I can provide to make the issue easier to resolve?

yea. You can send over the supertokens.init frontend code

```tsx
SuperTokensReact.init({
  appInfo: {
    appName: "appname",
    apiDomain: process.env.NEXT_PUBLIC_SUPERTOKENS_BASE_URL as string,
    websiteDomain: process.env.NEXT_PUBLIC_SUPERTOKENS_BASE_URL as string,
    apiBasePath: "/api/auth",
    websiteBasePath: "/auth",
  },
  recipeList: [
    ThirdPartyEmailPasswordReact.init({
      signInAndUpFeature: {
        providers,
      },
    }),
    SessionReact.init(),
  ],
});
```

and the component override code as well please

```tsx
<ThirdpartyEmailPasswordComponentsOverrideProvider
  components={{
    ThirdPartySignInAndUpCallbackTheme_Override: () => (
      <div>callback override content</div>
    ),
  }}
>
  <SuperTokensComponentNoSSR />
</ThirdpartyEmailPasswordComponentsOverrideProvider>;
```

Instead of wrapping the entire application, I chose to wrap only the auth slug. I have tested the same code wrapping the entire app with the same results.

ok ok thanks. Let's wait for <@435107855880683521>

hi, I'm not a 100% sure - nothing looks obviously wrong here - but the only thing I can think of right now is moving the override provider inside `SuperTokensComponentNoSSR`. I'll check this out in more detail and/or try to reproduce it locally a bit later (~1-1.5hr)

I reproduced it locally and it looks like a bug in the SDK; I'll try to figure out a fix soon.

That's a relief, I'd hate to waste time. I appreciate you looking into this 🙂

hey <@108062950622756864> we have released a new version of the supertokens-auth-react SDK which fixes this issue.

Please try it out 🙂

I was keeping an eye on that PR. Excited to check it out tomorrow 😁