AI-built apps · November 2026
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.
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 see | Cause |
|---|---|
supabaseUrl is required. in the Console | 1. Settings missing on the host |
| Home page works; a refresh or a shared link gives 404 | 2. No rule sending addresses to the app |
Red 404 lines for /assets/index-….js or .css | 3. 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 localhost | 5. Supabase permissions or login addresses |
| The host says the deploy failed and still shows an old version or nothing | 6. The build fails on the host |
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.
/dashboard works when you click to it and gives 404 when you
refresh it or share the link.
public/_redirects with one line:
/* /index.html 200
Fix on Vercel: a file vercel.json next to package.json:
{ "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }] }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.
base: '/my-app/' in vite.config.ts, give the router the same
folder (<BrowserRouter basename="/my-app">), and build again.data: null and an error, and the code calls
data.map(...) anyway, or reads user.id before the login has loaded.
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.localhost or the builder's preview.
./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.
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.
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.
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