[Bug] Email verification OTP is not sent to user's email

[Vyakhya-Sharma]

Description

The email verification flow shows a message indicating that a 6-digit OTP has been sent to the user's email, but no email is actually sent. The sendOTP() function in AuthContext.jsx only generates the OTP and stores it in localStorage — it never triggers any email delivery service.

Steps to Reproduce

1. Sign up for a new teacher account
2. Reach the "Email Verification" step on the profile/settings page
3. Enter an email address and trigger the OTP send
4. Check the email inbox for the verification code

Expected Behavior

A 6-digit OTP should be sent to the entered email address so the user can complete email verification.

Actual Behavior

No email is sent. The OTP is silently stored in localStorage (key: lecturePulse_otp_<email>) and is only visible via browser dev tools, making the email verification feature non-functional for real users.

Suggested Fix

Integrate a lightweight email-sending service (e.g., EmailJS, since the project is frontend-only) into the sendOTP() function in src/context/AuthContext.jsx to actually deliver the OTP to the user's email.

[Vyakhya-Sharma]

Hi @rishima17, I would like to work on this issue under SSOC'26. Please assign this issue to me.

[rishima17]

@Vyakhya-Sharma assigned to you , feel free to star the repo if u like the work 😊

[Rohith31-WD]

pls can you Asign me this @rishima17

[Vyakhya-Sharma]

Yeah, thanks @rishima17 for assigning me this issue. I'll submit the PR within 2 working days.

[Vyakhya-Sharma]

HI, @rishima17 while implementing the EmailJS integration for the OTP email issue, I realized the "from" email account used to send OTPs should ideally be a project-owned email rather than my personal one, since that account will need to stay connected long-term for this feature to keep working in production.

Could you share an email ID (or create one) that I should use to set up the EmailJS service for this? Alternatively, if you'd prefer, I can set it up with my own email for now just to get the feature working, and you can swap it out later from your end (it's just a few env variables to change).

Let me know whichever works best for you!

[rishima17]

HI, @rishima17 while implementing the EmailJS integration for the OTP email issue, I realized the "from" email account used to send OTPs should ideally be a project-owned email rather than my personal one, since that account will need to stay connected long-term for this feature to keep working in production.

Could you share an email ID (or create one) that I should use to set up the EmailJS service for this? Alternatively, if you'd prefer, I can set it up with my own email for now just to get the feature working, and you can swap it out later from your end (it's just a few env variables to change).

Let me know whichever works best for you!

Hey, thanks for checking this. Since this is an open source project, I don't have a dedicated project email yet.
For now, you can set it up with your email to get the feature working. Please keep the EmailJS configuration isolated through env variables so I can replace the credentials later if needed.