[Bug]: OTP send button stuck in loading state after successful 204 response

[ArrushiTripathi2429]

Bug Description

After clicking "Send OTP" on signup, the button stays in
"Sending Otp..." loading state indefinitely, even though
the backend returns 204 (success).

Steps to Reproduce

.1.Go to /signup
2. Fill in email and password
3. Check Terms of Service
4. Click "Send OTP"
5. Button stays in loading state forever

Expected Behavior

Loading state should stop and user should be prompted
to enter the OTP

Current Behavior

Button shows "Sending Otp..." indefinitely.
Network tab shows POST request completed with 204 status
Ultimately leads to failed to send OTP.

Environment

Browser: Chrome

• URL: https://riveto-frontend2.onrender.com/signup

Logs/Screenshots

[ArrushiTripathi2429]

Kindly assign this issue to me under Gssoc 2026.

[ArrushiTripathi2429]

Hey! I looked into this issue.

Root cause: In Registration.jsx, the handleSignup function
doesn't explicitly handle a 204 No Content response from
/auth/send-otp. The button stays in loading state because
the success path isn't triggered for 204.

Proposed fix in Registration.jsx:
if (res.status === 200 || res.status === 204) {
toast.success('OTP sent successfully');
setStep('2');
}

Unable to test locally due to missing Firebase credentials.
Could a maintainer confirm if this is the right fix?