[BUG] bug: Authentication issues (Sign-up broken, empty Magic Link validation, and non-functional Demo credentials)

[JMR825]

Description

While setting up and testing the application authentication flows locally and observing production, I encountered multiple critical bugs preventing users from creating accounts, using the Magic Link feature correctly, or logging in via demo credentials.

Bugs Encountered

Issue 1: Account Creation Failure

1. Navigate to the Sign-Up page (local or production).
2. Attempt to fill out the form and submit.
3. Observe that registration fails or crashes due to missing/misconfigured authentication providers.

Issue 2: Missing Validation on Magic Link Form

1. Navigate to the Sign-In / Magic Link page.
2. Leave the email field completely empty.
3. Click the "Send Magic Link" button.
4. Observe that the UI incorrectly displays the success message: "Magic link sent! Check your email." without triggering any client-side validation or backend checks.

Issue 3: Demo Credentials Broken

1. Attempt to log in using the provided demo/mock credentials.
2. Observe that authentication fails, likely because the application expects a live Supabase authentication provider instance even during local UI/Prisma testing.

Expected Behavior

1. Users should be able to register accounts locally or clear instructions should be provided if local auth needs to be mocked.
2. The Magic Link form should have required field validation preventing submissions with an empty email input.
3. Demo credentials should work seamlessly out of the box for local UI/UX testing.

Environment Details

• OS: Windows
• Database: Local PostgreSQL

Thank You

[rushikesh-bobade]

@JMR825 Thank you so much for the detailed bug report and for taking the time to test out the auth flows!

Regarding Issue 1 & 3 (Account Creation & Demo Credentials): You are completely correct. Because FlipTrack relies heavily on Supabase Auth, you cannot create an account or log in locally unless you either link a Supabase project or run the Supabase CLI local emulator. This is a known onboarding friction point that we are actively tracking right now in Issue #81. We are working on adding clear documentation for this soon!

Regarding Issue 2 (Missing Magic Link Validation): Great catch! You're absolutely right — the Magic Link UI is currently just a visual placeholder. It is missing both the client-side email validation and the actual backend supabase.auth.signInWithOtp call.

Since you were the one to spot it, would you be interested in submitting a PR to fix the Magic Link form? It would just require adding a simple required validation and wiring up the Supabase logic. Let me know if you'd like me to assign this part of the bug to you!

[JMR825]

Yes @rushikesh-bobade , please assign me the issue under ECSoC 26.

I hv also noticed that some of the cards are missing their images in cards.
Just like the screenshot provided.
May I ask if it an issue or left upto users??

Thank You

[github-actions]

Hi @JMR825! 👋

Thank you for your interest in contributing to this repository! Please wait until a maintainer officially assigns you to this issue before opening a Pull Request.

While you wait, please consider starring ⭐ this repository to show your support! We review requests regularly and will assign it as soon as possible if it's available. Happy coding! 🚀

[rushikesh-bobade]

@JMR825 Awesome! I just checked and since you have no other active issues, you are all clear. I have assigned this bug to you! Feel free to open a Draft PR whenever you start making progress on the Magic Link validation.

Regarding the missing images on the landing page cards: Great eye! Those are currently intentional CSS placeholders because we haven't created the final high-fidelity product screenshots for the marketing site yet. However, if you would like to contribute by creating and adding some proper, suitable images for those sections, you are more than welcome to include that in your PR! We would love the help.

Let me know if you run into any trouble with the Magic Link fix!

[rushikesh-bobade]

Hi @JMR825, I see you closed the PR and this issue. No worries at all if you got busy or decided to step away from this one! Open source can be tough, and we really appreciate you taking the time to write such a detailed bug report in the first place.

Since the Magic Link validation bug is still present in the codebase, I am going to reopen this issue and unassign it so that another contributor can pick it up.

If you decide you'd like to take another crack at it in the future, just let us know. Thanks again for your help!

[JMR825]

@rushikesh-bobade is the issue reoccurring??
or is there new bug in it?

[JMR825]

if there is new bug, Then I want to re-open the issue and solve it.
Will that be okay?
I'm really sorry for causing trouble..

[rushikesh-bobade]

Hi @JMR825,

Please do not apologize! You didn't cause any trouble. This is exactly how open-source development works—we iterate, review, and learn together!

To clarify: There is no new bug. Because your previous PR (#117) had syntax errors in routes.ts and had to be closed without merging, the original Magic Link validation bug is still present in the codebase. That is why I am reopening the issue.

However, after reviewing your PR description again, I realized you caught a massive bug in our codebase! You correctly noticed that our supabase.client.ts utility throws a process is not defined error in the browser.

I would be absolutely thrilled for you to take another crack at this PR! I am officially assigning this back to you.

Next Steps & Tips for your new PR:

1. Create a fresh branch off main.
2. Instead of putting the safe try/catch logic inside the UI component, please open app/utils/supabase.client.ts and fix the getSupabaseBrowserClient() function directly! You can add your safe try/catch checks there so the entire app benefits from it.
3. Once that utility is fixed, you can just import getSupabaseBrowserClient() into your Magic Link component to trigger the OTP.
4. Don't forget to run npm run typecheck or npm run build locally before pushing to ensure there are no syntax errors in routes.ts.

Take your time, and let me know if you need any pointers. You are doing great work!

[JMR825]

@rushikesh-bobade I hv now added all the changes and solved the bug. Can I close the issue now?