Hello! when i click login on the sign in / sign up screen (with a discord config, thanks not the problem: it works) in the console of the browser it gets a 404 to

http://localhost:8080/auth/authorisationurl?thirdPartyId=discord

though, it just works when i go there manually. why is that and is there a fix?

Hello! when i click login on the sign in / sign up screen (with a discord config, thanks not the problem: it works) in the console of the browser it gets a 404 to

http://localhost:8080/auth/authorisationurl?thirdPartyId=discord

though, it just works when i go there manually. why is that and is there a fix?

Yea sure, no problem: this is the backend

js
supertokens.init({    
    framework: "express",    
    supertokens: {        
        // try.supertokens.com is for demo purposes. Replace this with the address of your core instance (sign up on supertokens.com), or self host a core.        
        connectionURI: "https://try.supertokens.com",        // apiKey: "IF YOU HAVE AN API KEY FOR THE CORE, ADD IT HERE",    
    },    appInfo: {        // learn more about this on https://supertokens.com/docs/thirdpartyemailpassword/appinfo        
        appName: "Exalt Panel",        
        apiDomain: "http://localhost:8080",        
        websiteDomain: "http://localhost:3000",        
        apiBasePath: "/auth",        
        websiteBasePath: '/'    
    },    recipeList: [        
        ThirdPartyEmailPassword.init({
            providers: [
                Discord({
                    clientId: '<ID>',
                    clientSecret: '<secret>',
                    scope: [
                        'identify',
                        'guilds'
                    ]
                })
            ]
        }),        
        Session.init() // initializes session features    
    ]});

On the frontend, you want to set websiteDomain to

http://localhost:3000

as well.

I have done that since, but that doesn't solve the 404

Also, in the backend, you use

ThirdPartyEmailPassword

but in the frontend, you are using

ThirdParty

. You want to initialise the same recipe on both frontend and backend

Oh yea, that solved it, thanks! But, the backend wants a field named: "id", but it is not sent to the /auth/signinup endpoint. here's the error and request:

SuperTokens core threw an error for a POST request to path: '/recipe/signinup' with status code: 400 and message: Field name 'id' is invalid in JSON input

and the request:

{"code":
<codeHere>","thirdPartyId":"discord","redirectURI":"http://localhost:3000/callback/discord","clientId":"discord"}

hmm. That's odd

It appears that it doesnt reach that, it errors here:

at Querier.<anonymous> (D:\react-dev\exalt-web\exalt-frontend-backend\backend\node_modules\supertokens-node\lib\build\querier.js:252:31)
    at Generator.throw (<anonymous>)
    at rejected (D:\react-dev\exalt-web\exalt-frontend-backend\backend\node_modules\supertokens-node\lib\build\querier.js:22:44)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Can we get on a quick call to debug?

I'd be more then happy to do that, but i'm in school right now 😛

haha ok. Then well...

I'd be available in about 3 hours, are you available hen aswell?

> I'd be available in about 3 hours, are you available hen aswell? Sure. You can book a call with me as per your time preference: https://supertokens.com/call-user

wow thats pretty cool

to book a call? No..

I booked a call, should be 5 GMT

sounds good! talk to you then

it sent me a zoom link, can we call via discord though

Discord calls behave weirdly for me.. we can try it out though.

@User so on my home PC it does reach the console.log(userinfo). this is what it spits out:

json
{
  id: '576624954997604353',
  username: 'IKEW',
  flags: 128,
  banner: null,
  banner_color: null,
  accent_color: null,
  locale: 'en-US',
  mfa_enabled: true
}

Right. So that seems right. Does the whole flow work for you?

This is visually what i'm seeing:

Can I see the network response output?

Yea sure:

i see.

Yes so

is there any stack trace produced on the backend. cause it shouldn't give a 500 error

i added "email" as scope and now there's no errors!

ahh right

oh

unless you give a scopes array yourself

well i added it manually and now it seems to work

which you have

Yea

ok cool!

Yea, thanks man!

shall I cancel our call?

Yes please