π Fix Clerk OAuth User Creation Issue in MongoDB #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue where users signing up with Google OAuth were not found in MongoDB due to webhook delays.
β Implemented createOrGetUser to check for existing users before creating new ones.
β Updated the user.created webhook handler to use createOrGetUser instead of createUser, preventing duplicate user creation.
β Modified getUserById to fetch user data from Clerk and create them if missing in MongoDB, improving resilience.
β Ensured smoother user creation flow for both email/password and OAuth signups.
This resolves the "User not found" error caused by a race condition between OAuth completion and webhook delivery.