UrgisoftAI-built apps

AI-built apps · November 2026

Your Lovable or Bolt app shows a blank page after you publish it

Short answer: the app itself is usually fine. Something it needs is missing on the live address: its settings, a rule that sends every address to the app, or a Supabase permission. The browser tells you which one in about two minutes, and each has a small fix.

Find the cause in two minutes

Open the live site on a computer, press F12 (Mac: Option + Command + I), open the Console tab and reload the page. Then look at the Network tab for red lines. Match what you see:

What you seeCause
supabaseUrl is required. in the Console1. Settings missing on the host
Home page works; a refresh or a shared link gives 4042. No rule sending addresses to the app
Red 404 lines for /assets/index-….js or .css3. Wrong base path
Cannot read properties of undefined or null (reading 'map' or 'id')4. The app crashes while drawing
No red at all, but lists are empty, or login sends you to localhost5. Supabase permissions or login addresses
The host says the deploy failed and still shows an old version or nothing6. The build fails on the host

The six causes, and the fix for each

  1. The app's settings are missing on the host. Apps built with Vite read their Supabase address and key from settings named VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY (some projects call the second one VITE_SUPABASE_PUBLISHABLE_KEY). The builder has them; your Vercel or Netlify project does not, so the app stops on its first line and the page stays white.
    Fix: copy the names exactly as your code uses them into the host's Environment Variables, then deploy again. These values are baked in when the app is built, so saving them without a new deploy changes nothing.
  2. No rule sends every address to the app. An app like this is one page that draws all the others. The host only knows the home page, so /dashboard works when you click to it and gives 404 when you refresh it or share the link.
    Fix on Netlify: a file public/_redirects with one line:
    /*    /index.html   200
    Fix on Vercel: a file vercel.json next to package.json:
    { "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }
  3. The app looks for its files in the wrong folder. If the site lives under a folder (GitHub Pages: you.github.io/my-app/), the page asks for /assets/… at the top of the site and gets 404s, so no code runs at all.
    Fix: set base: '/my-app/' in vite.config.ts, give the router the same folder (<BrowserRouter basename="/my-app">), and build again.
  4. The app crashes while drawing the page. When one part of a React page throws an error and nothing catches it, React removes the whole page: white screen. The usual trigger is live data that isn't there yet: Supabase answers with data: null and an error, and the code calls data.map(...) anyway, or reads user.id before the login has loaded.
    Fix: check error after every Supabase call, fall back to an empty list (data ?? []), wait for the session before reading the user, and wrap the app in an error boundary so one broken part shows a message instead of taking the page down.
  5. Supabase lets the builder in, but not your live address. Two separate things hide here. Row Level Security: a table with security on and no policy returns an empty list with no error, so the page loads and shows nothing. Login: Supabase sends people back to the address in its settings, which is often still localhost or the builder's preview.
    Fix: write a policy for each table the page reads (who may see which rows), and in Supabase under Authentication, URL Configuration, set the Site URL to your live address and add it to the Redirect URLs. Never turn security off to make the list appear: that opens the table to everyone.
  6. The build fails on the host. It builds in the builder and on your laptop, and fails on Vercel or Netlify. Three usual reasons: the host's computers care about capital letters in file names (./Button is not ./button.tsx), the host runs a stricter check first (tsc && vite build stops on type errors the preview ignored), or it uses an older Node version.
    Fix: open the host's build log and read the first error, not the last. Make import names match the file names letter for letter, fix or loosen the type error it names, and set the Node version the project expects in the host's settings.

This is a checklist from engineering practice, not a study: we have not counted how often each cause happens. The file names and settings above are the standard ones for React apps built with Vite and Supabase, which is what Lovable and Bolt produce by default; other stacks differ in the names, not in the causes.

It loads now, but it is slow on phones?

That is a different problem with its own five causes. We built a demo shop, measured it and fixed it: main content 14.5 s before, 1.4 s after, with both pages live to test.

Want it fixed for you?

We fix apps made with Lovable, Bolt, Replit, Cursor and other AI builders, in your own code, and tell you in plain words what was wrong. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app deployed and working live from $150. No fix, no charge. A GitHub invite is enough; we never ask for passwords.

See the gig on Fiverr