clerk + convex + expo
Hey I've set up the convex clerk thing in expo. I can sign up and sign in etc etc. the problem I'm trying to deal with now is creating the user table when signing in. I researched everywhere and I'm not sure of the solution still.
My fear is that if I sign up, I might have the email registered on clerk but something might fail and the user is not registered on convex. Do I create a web hook to solve this issue, do I use another approach like making use of the clerkID and CTX.getauthuseridentity thingy?
8 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
a clerk webhook will do the trick
would you recommend me stick to clerk or use convex-auth. I've had people are struggling with how clerk works in production. What do you think?
if you want something simple that's just going to work, I'd check out better auth
https://convex-better-auth.netlify.app/ and #better-auth
Convex + Better Auth
Typesafe, secure auth for Convex apps with Better Auth
you don't think the fact that its in alpha is a problem? The problem i have is i have to create this app for someone and they want users etc etc, so its a long project. I know convex is the best backend choice because ive used it before, but better auth in alpha is difficult since they might introduce some breaking change?
Fwiw, the Better Auth component isn't in alpha for reliability issues, it's in alpha because the api still has some potentially breaking changes in the near term pipeline. Pushing to get it to stability. But it does work great.
I see, I adopted it anyways, thanks a lot for the work you're doing on the component