₦airaland Forum

Omo, I’m locked in Kpa.
Moved local Postgres → Supabase, deploy to Vercel. Thought it’d be smooth.

Now:
Production domain = white screen
Preview = blank too
Vercel using commit links instead of domain
Supabase auth failing

Wahala breakdown:
Branch chaos – Vercel only shows last feature branch active, not main
Promotion fail – promoted that branch → now full chaos
Env mismatch – unsure if production is reading correct Supabase keys
Auth redirect issues – login not working

What I’ve tried:
Added Supabase keys to .env and Vercel env settings
Promoted branch to production
Build completes, but still blank

Questions I need help with:
How to force Vercel prod + preview to use main branch?
Why preview works sometimes then shows blank?
Could Supabase auth redirect URL be the culprit?
How to fix Vercel using commit links instead of domain for deployments?

Demo in 5 days. Time no dey.

If you’ve survived Supabase + Vercel branch + blank screen + auth wahala, holla me 🙏

YudiPort:
Omo, I’m locked in Kpa.
Moved local Postgres → Supabase, deploy to Vercel. Thought it’d be smooth.

Now:
Production domain = white screen
Preview = blank too
Vercel using commit links instead of domain
Supabase auth failing

Wahala breakdown:
Branch chaos – Vercel only shows last feature branch active, not main
Promotion fail – promoted that branch → now full chaos
Env mismatch – unsure if production is reading correct Supabase keys
Auth redirect issues – login not working

What I’ve tried:
Added Supabase keys to .env and Vercel env settings
Promoted branch to production
Build completes, but still blank

Questions I need help with:
How to force Vercel prod + preview to use main branch?
Why preview works sometimes then shows blank?
Could Supabase auth redirect URL be the culprit?
How to fix Vercel using commit links instead of domain for deployments?

Demo in 5 days. Time no dey.

If you’ve survived Supabase + Vercel branch + blank screen + auth wahala, holla me 🙏

I sent you an email already

I truly understand what you’re dealing with because I’ve faced and resolved similar Supabase and Vercel deployment issues. From blank production screens and unstable preview builds to branch misalignment and authentication redirect failures. When branches, environment variables, and domain configurations fall out of sync, the symptoms look exactly like what you’re describing.
In my experience, the solution isn’t trial and error. it requires a systematic approach: correcting the production branch mapping, ensuring environment parity between local and Vercel, validating Supabase keys, and properly configuring auth redirect URLs. Once those are aligned, stability returns quickly.
I’ve successfully navigated this stack under similar pressure, so I can provide clear, structured guidance to help you resolve it efficiently and confidently,especially with your demo timeline in mind. You can respond to your mail if you feel you'd need my further assistance

YudiPort:
Omo, I’m locked in Kpa.
Moved local Postgres → Supabase, deploy to Vercel. Thought it’d be smooth.

Now:
Production domain = white screen
Preview = blank too
Vercel using commit links instead of domain
Supabase auth failing

Wahala breakdown:
Branch chaos – Vercel only shows last feature branch active, not main
Promotion fail – promoted that branch → now full chaos
Env mismatch – unsure if production is reading correct Supabase keys
Auth redirect issues – login not working

What I’ve tried:
Added Supabase keys to .env and Vercel env settings
Promoted branch to production
Build completes, but still blank

Questions I need help with:
How to force Vercel prod + preview to use main branch?
Why preview works sometimes then shows blank?
Could Supabase auth redirect URL be the culprit?
How to fix Vercel using commit links instead of domain for deployments?

Demo in 5 days. Time no dey.

If you’ve survived Supabase + Vercel branch + blank screen + auth wahala, holla me 🙏

Pull the entire script into your PC locally and carefully debug

White screen after a successful build usually means the app is crashing at runtime, not at build time. The build passes but the JS errors out in the browser.

First thing: open your production URL in a browser, hit F12, check the console errors. That'll tell you exactly what's breaking.

For the branch issue: Vercel dashboard → your project → Settings → Git → set Production Branch to main. Whatever branch is set there is what gets deployed to your custom domain.

For Supabase auth: go to Supabase dashboard → Auth → URL Configuration → add your production domain AND a wildcard for Vercel previews (*.). Without this, auth redirects silently fail.

Env vars: any variable you add in Vercel dashboard doesn't apply to existing deploys — you need to trigger a fresh redeploy after adding them.

Demo in 5 days, you still get time to fix am. Check the browser console first, that's your real error log.