Hey, I just noticed that there is potentially a bug (or misconfig) on the redirect catcher on react package. This implementation: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/handling-signin-success - we are using just as it is the item no. 1. With email and password it redirects, but with social login (FB and Google), it doesn't. I recorded a short video showing up: https://www.loom.com/share/93465728ba4d460191169a34e2fbf346?from_recorder=1 Here is on our front-end init, we didn't modify any of it:

ThirdPartyEmailPasswordReact.init({
        getRedirectionURL: async (context) => {
          if (context.action === "SUCCESS") {
            return context.redirectToPath === undefined
              ? "/"
              : context.redirectToPath
          }
        },
[...]

From what I see, it seems when the social login callsback, it removes the redicrectToPath param, which defaults the redirect back to the home page.