feat: email verification for email/password signup (#691) - #774
feat: email verification for email/password signup (#691)#774saurabhhhcodes wants to merge 1 commit into
Conversation
…ngh#691) - signUp: sends a Firebase verification email after account creation and signs the new user out, keeping them on the auth screen with a 'check your inbox' message until verified - signIn: reloads the user and blocks access with auth/email-not-verified when emailVerified is false, then signs out - resendVerificationEmail(email, password): re-authenticates, resends the verification email, and signs out again - AuthScreen: verification-required banner with a resend button; signup success switches to the sign-in tab with the inbox message - Emulator mode (no real email delivery) skips verification gating so existing emulator flows keep working
|
Warning Review limit reached
Next review available in: 37 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
1 participant
Closes #691
What
Email/password signup now requires email verification before the user can access the app.
app/src/lib/AuthContext.jssignUp: sends a FirebasesendEmailVerificationemail after account creation, then signs the new user out — they stay on the auth screen with a "check your inbox" message until verifiedsignIn:reload()s the user and blocks access with a newauth/email-not-verifiederror whenemailVerifiedis false (signs out so the app never proceeds in an unverified session)resendVerificationEmail(email, password): re-authenticates, resends the verification email, signs out againEXPO_PUBLIC_USE_EMULATORS) skips verification gating — real emails can't be delivered, and the Google emulator flows rely onsignUpapp/src/screens/AuthScreen.jsauth/email-not-verified/auth/verification-email-sentmessages added to the error mapFlow: sign up → verification email sent → user sees inbox message → clicks link → signs in → app checks
emailVerified→ grants access. Resend available if the first email is lost.Verify
node --checkon both files, prettier clean