[SOLVED] account scope missing on Google oAuth sign in

[normal mortar]

I am currently facing an issue which is only happening to one of my testers. When she tries to sign in either with google or using email and password on both her phone and system, it throws an error.

When I run the process on my end and ask others to do it, it works well but when she does it on her end it doesn't work.

Signing up with email and password returns an invalid_parameters error, but it works for other people.

I have tried to replicate it locally and in production but I have not been able to do it.

We checked her cookies and site data but nothing has been set so far so it's clean.

Code for oAuth sign in.

export default function signInWithOAuth(providerName: "facebook" | "google") {
  authAccount.createOAuth2Session(
    providerName,
    `${BASE_URL}/oauth/`,
    `${BASE_URL}/login`
  );
}

BASE_URL = 'https://memora-tau.vercel.app

It works for other user and it's just her. I have tried to find out what's wrong but I don't know

[blazing hearth]

Please create a separate post for the invalid parameters error

[blazing hearth]

The oauth problem is probably a 3rd party cookie problem.

For local development, maybe you can change your browser settings to enable 3rd party cookies.

In production, you'll need to use custom domains

[normal mortar]

Okay

[normal mortar]

It's a side project I'm working on so I won't be doing a custom domain. Is there nwi other way?

I hosted the app on Vercel tho

[normal mortar]

But why does it work for some people and it doesn't work for others

account scope missing on Google oAuth sign in

[blazing hearth]

Some people or some browsers are more lenient on 3rd party cookies

[blazing hearth]

Unfortunately not

[normal mortar]

Hmm, interesting. And the browsers used were chrome

[normal mortar]

Ah I see. So if I got through with it, once I connect the custom domain it should start working yes?

[blazing hearth]

Yes, assuming this is indeed the problem

[normal mortar]

Is there something else that could be the problem if not this?

Maybe I can try that since I don't have access to a custom domain

[blazing hearth]

Not that I can think of. The most common reason is 3rd party cookies.

In chrome, there's some setting in the browser for enabling/disabling 3rd party cookies. They can try that

[normal mortar]

Okay, thank you. I would tell her to try it

[normal mortar]

I have fixed this by taking this route. Her browsers blocks all third party cookies so it couldn't work. I told her to allow the site to use third party cookies and it worked.

So this is closed