[BUG]: Login form accepts invalid email formats without client-side validation

[aayan-rashid]

Description

The login form accepts invalid email formats without displaying any client-side validation message. Users can enter arbitrary text in the email field, and the request is only rejected after being sent to the backend.

Steps to Reproduce

1. Open the Web App page.
2. Enter an invalid email such as:
   • ABC172871t4!!!cbw
   • abc@abc
3. Enter any password.
4. Click Login to Arvio.

Screenshot

Expected Behavior

The email field should validate the input before submitting the request and prompt the user to enter a valid email address.

Actual Behavior

The form accepts invalid email formats and sends the request to the backend, which later rejects the login.

Additional Context

Although the backend correctly validates credentials, adding client-side email validation would provide immediate feedback and improve the overall user experience by preventing unnecessary requests.

[aayan-rashid]

I would like to contribute to this under GSSoC 2026.

Please assign it to me.

labels:
gssoc:approved
level:beginner

[Himanth-reddy]

Hi @aayan-rashid,

Thanks for reporting this issue and for your interest in contributing!

Here is the recommended technical approach for implementing this:

1. Authentication Flow (auth.arvio):

   • Instead of handling raw credentials directly, redirect users to the central authentication portal at auth.arvio.tv (https://auth.arvio.tv/?redirect_uri=<APP_URL>).
   • Once validated, auth.arvio.tv redirects back with session tokens in the URL fragment.

2. Stremio Migration Placement:

   • Place the "Migrate from Stremio" feature inside the logged-in user dashboard / settings page.
   • Performing the migration after login ensures that imported Stremio addons and manifests are immediately linked to the user's ARVIO Cloud account and synced across devices (account-sync-push).

Let me know if you are okay with this approach, and I can assign this issue to you!

[aayan-rashid]

Hi @Himanth-reddy , I traced the Dashboard (https://arvio-ui.web.app/) and web app (https://web.arvio.tv/) flows and I understand the requested flow: the Dashboard should stop handling ARVIO credentials directly and redirect to auth.arvio.tv, similar to the existing "Connect to Cloud" flow in web.arvio.tv. After successful authentication, the central auth portal redirects back with the session tokens, and the Dashboard uses the authenticated user state.

But, it looks like that the arvio-ui.web.app application containing the current "Login to Arvio" / "Login to Stremio" forms is not part of the ARVIO repository. The current repository only links/embeds arvio-ui.web.app.

Since your recommended approach for #530/#531 is to move authentication to auth.arvio.tv, could you please provide the source repository for arvio-ui.web.app (or confirm where the Dashboard source is maintained)?

I want to make sure I implement the authentication-flow changes in the correct project before starting the PR.

refernce image:
clicking on dashboard in homepage opens this-

[aayan-rashid]

Hi @Himanth-reddy, could you let me know if this issue is relevant anymore or shall I close it, because I don't see the Dashboard/web app option in the homepage header.

Reference: