₦airaland Forum

AUSVINS:
Hi I sent you a message

I just responded

Detechi48:
Interested

Alright I sent you a pm

Come in
There's currently a 25% discount on every jobs given to me

Yes

Come in let's fix that old website today

Come in
There's currently a 25% discount on the registration

Hi

Yes

Come in

Now

Now

Racheal45:
I can help you with verified lawyer in Malaysia
But firstly you have to brief me what happen either guilty or not
Please no lies or emotion
Your brother already in trouble all you need is to get him out

scam run

Ok no problem
more characters needed

Arsenal won the league already..
Guardiola even knows this. There's no mathematical miracle that can change it.

Hi

Yes

Hi

Hi

Come in

Hi

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 🙏

I sent you an email already

Come in

Gwagonbabe:
I have responded to you.

kindly check now

Gwagonbabe:
Pls I run a business with my spouse and it was what I was doing before I left Nigeria for study. I have all documents to show for it.. please can anyone tell me or give me the template for a reference letter fo self employed business

I just sent you a mail message. Respond

Slimani:
Ok, will check.

you've got any old website for modifications?

HADI854:
Pls any suggestions of places I can apply for My SIWES program for the year (probably 4-5 months from now)?
Mechanical Engineering to be precise (300L)

send me a message right away

Hi

Yh