It seems like the post-login token ingestion / confirmation isn't working, I'm presuming its because we're using HashRouter (routes are /#/foo). Has anyone had this problem?

Hey @qoby what do you mean by "post-login token ingestion" ?

yeah, exactly

I see. So the issue is that it's not routing to the right page? Or that it's not being able to pick up the right code from the URL?

Thanks @rp – yeah, its React with react-router-dom. It ends up with a blank screen on /#/auth/verify and doesn't forward off to any other urls

Right, so the problem here is that the SDK uses the location hash for passwordless in the magic link flow But because the hash router has the path as part of the URL hash, the SDK logic fails. When you initialise SuperTokens you can pass custom handlers for the Window API to handle this You can use the logic from this file: https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-thirdpartypasswordless-electron/src/windowHandler.ts And then pass that when calling

SuperTokens.init

similar to

SuperTokens.init({
    // ...
    windowHandler: getWindowHandler, // Refer to src/windowHandler.ts
    // ...
});

Thanks @nkshah2, I'll take a look https://localhost:3000/verify?rid=passwordless&preAuthSessionId=code=#code

Right, whats the

apiBasePath

set to for both your frontend and backend?

apiBasePath or web base? /auth

apiBasePath

I think that's right – I messed it up trying to push a hash into the web base path, since it was linking /auth/verify and not /#/auth/verify

Hmm. That’s odd. Can you open an issue about that please?

@nkshah2 just looking through that code, why not unhash with something like: new URL(window.location.hash.substring(1), window.location.origin)

No specific reason, just wanted to keep it simple for an example app

I'm probably missing something obvious, but I think it can be rewritten like getSearch() { return (new URL(window.location.hash.substring(1), window.location.origin)).search; }, getHash() { return (new URL(window.location.hash.substring(1), window.location.origin)).hash; }, getPathName() { return (new URL(window.location.hash.substring(1), window.location.origin)).pathname; },

Yeah that should work

@rp you mentioned "override the function that sends the email", are you talking about

recipeList smsDelivery.override.sendSms

?

There is also emailDelivery.override.sendEmail. Use that one

oops yes, thank you

Do you mean an example of returning a custom urlWithLinkCode for the email?

yeah, is that the right idea?

What do you want to do?

Right, based on your advice above

If yes, you can do it like this;

ts
Passwordless.init({
    emailDelivery: {
        override: (oI) => {
            return {
                ...oI,
                sendEmail: async function (input) {
                    let magicLink = input.urlWithLinkCode // this is like {websiteDomain}/{websiteBasePath}/verify#<one time use code>
                    // you can parse the URL using the URL lib and modify the link however you like
                    // and then you can assign it back to input
                    input.urlWithLinkCode = magicLink
                    return oI.sendEmail(input);
                }
            }
        }
    }
})

thank you!