chen-rn / CUA

(no longer maintained) create-universal-app(CUA) is an opinionated template for creating fullstack universal apps (Expo, Next, tRPC, Prisma, Clerk, Solito, Tamagui)

Home Page:https://cua-demo.vercel.app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

signup with clerk and gmail auth strategy doesnt work

hitesh97 opened this issue Β· comments

commented

Discussed in #65

Originally posted by hitesh97 March 20, 2023
Hi Chen,

Amazing work of setting up this repo and mono-repo as well as the video πŸ‘

I followed all the steps and created the setup word by word.

When I try to sign-up with gmail strategy using clerk, it seems to redirect me to
http://localhost:3000/signup/sso-oauth/oauth_google Infinitely!

can you please let me know, if there is something I am missing? does clerk needs a redirect URL to be setup somewhere?
or is there anything in the nextjs router missing something?

i.e Sign-up => SignIn => not authenticated => Sign Up => sign In ....etc...etc..

Hope you can help as I would like to work on this set up for my pet project!

thanks for. amazing work anyways!

I am facing the same issue, followed the instructions to set up the project. After sign-in/sign-up, I get an infinite redirect.

Here's what I've tried so far:

  • Tried using mysql instead of sqlite
  • Tried using a personal clerk account instead of the keys bundled with the repo
  • Tried using the CLI to scaffold instead of cloning the repo

Great work on setting this up, let me know if there are other steps we can take to narrow down the issue. Thank you!

commented

so, I had not set up Google authentication keys etc and not associated google auth with clerk..
But even after setting up google authentication with clerk, there seems to be error, when its trying to save user's information, i.e. session and user info..on to postgre sql server..
so I am investigating that .. and if I get it to work, I will post PR for that.. πŸ‘

I've been facing the same issue with every authentication method, however I haven't tried with newer versions of CUA so some of what I was facing may have been fixed.

facing same issue