VibeFix

Guide

App stuck loading after publish: the spinner never stops

Published by Yosef D., founder of VibeFix

How this guide was made: Written with AI assistance and checked against the sources linked on this page.

Updated

A live app that spins forever is waiting for an answer that never comes. Open the browser console on the live address. The usual causes are a database address or key set only for the preview, a paused Supabase project, a sign-in check that never finishes for signed-out visitors, or a crashed backend function.

Fixed in your code, then tested live. Get it fixed: a free check first confirms the problem on your live app, usually in 4 to 10 minutes.

Free. No account needed. It usually takes 4 to 10 minutes.

Want it fixed? For Lovable apps or code on GitHub, our AI agent fixes it in your code for $79 and tests your live app again. If we can't complete your re-check, you get your money back.

Why it happens

A spinner that never stops almost always means the page asked for something and never got an answer.

Possible causes

How to fix it

  1. Open the live address in a private window. Open the browser console (in Chrome: right-click, Inspect, Console) and the Network tab, then reload.
  2. Look for a request that is red or stays "pending". The address it calls tells you which part is stuck: your database, sign-in, or a backend function.
  3. If the request goes to localhost, or the key is "undefined", the live site is missing a setting. Add the database URL and public key to the published app's environment settings and publish again.
  4. If it is a Supabase project, open the Supabase dashboard. Supabase pauses Free-plan projects with low activity over 7 days. If the project shows Paused, press Resume and wait for it to come back.
  5. If the spinner waits on sign-in, add your live address to Supabase > Authentication > URL Configuration (Site URL and Redirect URLs). Then make sure the app stops showing the spinner when there is no signed-in user: the loading flag must be set to false whether or not a session is found.
  6. If a backend function returns a 500 error, open that function's logs and fix the first error shown.
  7. If the console shows a failed script file (a "Loading chunk" or 404 on a .js file), do a hard refresh (Ctrl+Shift+R). If that fixes it, the old page was cached after a new publish: publish once more.
  8. Check again in a private window on a phone and on a computer.

You can't see it yourself

You're signed in, your customers aren't. You are usually signed in, with a warm browser. The spinner can show only for a new, signed-out visitor, so you never meet it.

Related: Base44 app not working or broken? Causes and fixes · My app shows a blank white page after publishing · It works in the preview but breaks after I deploy · My builder says the app is tested, but my customers hit problems

VibeFix is independent. Lovable, Bolt, Replit, Base44, v0, Supabase, Firebase, Stripe and Vercel are trademarks of their owners.

More guides · Shopify store accessibility · About · Your privacy choices