AI-built apps ยท November 2026
Short answer: nearly every login problem in an app built with Lovable or Bolt comes from a setting outside the code: Supabase's list of allowed addresses, Google's sign-in settings, Supabase's email sender, or the table permissions (row level security). Find your symptom below; each one has a fix you can check in a few minutes.
Open the browser's console (right-click the page, Inspect, Console) and try to log in. The red line, or the address you land on, tells you which one it is:
| What you see | Cause |
|---|---|
After logging in, or clicking the email link, you land on localhost:3000 or the builder's preview address | 1. The live address is not in Supabase's allowed list |
Google says Error 400: redirect_uri_mismatch | 2. Google does not know Supabase's return address |
The sign-up email never arrives, or email rate limit exceeded | 3. Supabase's built-in email sender is for testing only |
Database error saving new user when someone signs up | 4. The script that creates the user's profile fails |
Logged in, but lists are empty, or new row violates row-level security policy | 5. Row level security blocks the user |
| Refreshing the page logs you out, or sends you to the login page for a moment | 6. The app checks the session before it has loaded |
Invalid API key, Failed to fetch, or every request to Supabase fails | 7. Wrong settings on the host, or a paused project |
http://localhost:3000 or the builder's preview.
https://yourapp.com) and add it under Redirect URLs with /** at the end so
every page counts (https://yourapp.com/**). Keep the preview address there too if you still test in
the builder. In the code, any emailRedirectTo or redirectTo should use
window.location.origin, not a fixed address.https://<your-project>.supabase.co/auth/v1/callback under Authorized redirect URIs (Supabase shows
the exact address on its Google provider page). Add your live address under Authorized JavaScript origins. Your
own app's address goes in Supabase's Redirect URLs (cause 1), not in Google's list. While the Google app is in
Testing mode, only the test users you listed can sign in.Email not confirmed).
profiles table. If that function breaks (a required column it does not
fill, a misspelled column, a table it cannot see), Supabase cancels the whole sign-up and shows only this short
message.
security definer and set search_path = public, writing the table as
public.profiles.new row violates row-level security policy (code 42501), often because the rule checks
auth.uid() = user_id and the app never fills user_id.
using (auth.uid() = user_id), and give inserts the same check with with check. Give
user_id a default in the table (default auth.uid()) so the app cannot forget it.
Never fix this by turning row level security off: a table without it can be read and changed by anyone who
opens your site, because the key in the browser is public by design. Supabase marks such tables
"Unrestricted".supabase.auth.onAuthStateChange once, at the top of the app, and only redirect after the loading
state ends. Create the Supabase client once, in one file, not inside a component. If the console shows
Invalid Refresh Token, the saved session is old: sign out and in again; if it keeps coming back, two
clients are fighting over the same session.VITE_SUPABASE_URL and the anon key under exactly the names the code reads; a missing or misspelled
one gives Invalid API key or requests to undefined. Separately, Supabase pauses free
projects after about a week without activity, and every request then fails.
import.meta.env.), then deploy again, since these values are built in at deploy time. If the Supabase
dashboard says the project is paused, restore it there. The steps for the host are on
our deploy page.This is a checklist from engineering practice, not a study: we have not counted how often each cause happens. The messages are the tools' own wording and can differ a little between versions, and Supabase and Google rename their menus from time to time. It covers React apps with Supabase sign-in, which is what Lovable and Bolt set up by default.
The app shows nothing at all? A blank page after publishing: six causes and the fix for each. Moving it to your own host? Deploy to Vercel or Netlify: the steps, and six errors that stop it. Slow on phones? Our demo shop, measured before and after: 14.5 s to 1.4 s.
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