[SOLVED] Google Auth not working in a React/TanStack Start App

Authentication with Google has failed. It redirects back to the signin route in React. Attached screenshots for configuration of Google console and Appwrite Google Auth configuration.

Here is the link to the repo.

https://github.com/davidofug/google-auth-with-appwrite

@Steven please help

Avoid pinging core members 😅

Hey! Thanks for telling that. I did this sometimes when I felt like I couldn't find solution for the user's issues or when any issue seems urgent😅

This one is not urgent

Yes I know. I was talking about earlier incidents, definitely not this one

@David Try enabling third party cookies as it looks like your browser is blocking some of the requests

Also, we need the console network logs for further debugging.
Make suer to censor all the sensitive tokens, IDs, etc

Yes @David , Also make sure you properly hide your email IDs (if you don't want them to be disclosed) in your videos.

Also, I've checked your code. And I've a suggesstion. Here, in this part in auth.jsx: ```await account.createOAuth2Session(
"google",
${window.location.origin}/oauth-callback,
${window.location.origin}/failed
);

If that too won't work. Try directly using http://localhost:5173

90% its third party cookies related issue
Cause as soon as login occurs, the missing user role error is there.
@David
https://appwrite.io/blog/post/fixing-oauth2-issues-in-appwrite-cloud
Try reading the details and implementing what is written.

Thank you for the warning 🙌

Looks like none of these worked!

Then it must be the browser blocking your requests as D5 & Axistro mentioned

I supposed brave blocks the cookies but I doubt if Firefox is also blocking the cookies. Let me try the option recommended by @Axistro

its not just these browsers blocks these
but most browser have a third party cookies policy (to save you)
Although in browsers like brave it will still clear the cookies created by the new method suggested in the blog. But you should still be able to keep logged in until you close the site.
but it wont get cleared in chrome. so you can test there.
the final and solid solution is to have custom domain.

I have set the custom domain. But when I am localhost will it work?

You will be able to keep signed in untill you keep the site open(for brave)
Other browsers should keep the sessions.
As for the localhost, it will still act like third party as domains dont match. (Should work fine on production)

jst today, worked fixing the oauth.. 4hrs jst to realise firefox blocked the cookies.

Did you resolve the issue? After following everything, it logged in once then it started failing again. I have tried firefox, safari and firefox

is the issue same as before
or if you close the site , you have to login again?

turned off the site protection feature on firefox.

removed ublockorigin

then it worked, but then tried again in chrome with default settings. it worked.

no changes to the code