Field Notes
Notes from the incident desk .
What breaks in web applications that are already live including the ones built with Lovable, Bolt or another AI builder. The failure patterns we trace most often across authentication, Supabase, Stripe, APIs and deployment, how each one gets diagnosed, and what to verify before it reaches your users.
-
Lovable App Maintenance Checklist After Launch
Use this Lovable app maintenance checklist to monitor releases, Supabase, Edge Functions, Stripe webhooks, backups, and production drift.
Read
-
Lovable Export Won’t Run Locally: Diagnostic Checklist
Lovable export won’t run locally? Isolate install, build, environment, Supabase, routing, and managed-runtime failures without broad changes.
Read
-
Lovable File Upload 403: Fix the Storage RLS Error
Lovable file uploads fail with 403 or a row-level security error? Check the bucket and user folder, test a narrow fix, and keep customer files private.
Read
-
Lovable JWT Expired and Invalid Refresh Token Errors
A published Lovable app logs users out with JWT expired or Invalid Refresh Token. Check session refresh, cookies and sign-out scope before editing auth.
Read
-
Lovable “User Already Registered”: What to Check
A published Lovable app says User already registered, but the customer cannot sign in. Check the Auth user, email state and app records safely.
Read
-
Lovable “Failed to Fetch” on a Custom Domain
A Lovable preview can call the API while the custom domain shows Failed to fetch. Compare the Origin and OPTIONS response before changing app code.
Read
-
Lovable Supabase Connection Broke: Invalid API Key
A published Lovable app returns Invalid API key from Supabase. Check the live project URL and publishable key as one pair before changing RLS or auth.
Read
-
Lovable Error 400: redirect_uri_mismatch After Publish
Google login in a published Lovable app returns Error 400: redirect_uri_mismatch. Compare the actual callback URL with Google and Supabase settings.
Read
-
Lovable Edge Function Returned a Non-2xx Status Code
A Lovable Edge Function returned a non-2xx status code in production. Use the response and logs to separate 401, 500 and timeout failures.
Read
-
Application Error: Client-Side Exception After Deploy
A client-side exception appeared after deploy. Capture the browser error, release and failed request, then separate stale files from broken code.
Read
-
502 Bad Gateway on a Live Web App: Which Layer Failed?
Diagnose a 502 Bad Gateway in Next.js, Vercel, Lovable, Supabase and Railway apps using request IDs, function logs and public production cases.
Read
-
Supabase SCRAM Wrong Password After Deploy: What Changed?
Your app worked until a deploy or password change. Check DATABASE_URL, URL encoding, pooler credentials, cached passwords and temporary IP bans.
Read
-
Lovable App Fix Cost in 2026: Fix or Migrate?
See what drives Lovable app fix cost in 2026, how migration quotes differ, what evidence lowers uncertainty, and when to hire a developer.
Read
-
rls_auto_enable in Supabase: What It Does, Keep or Drop
Found rls_auto_enable() and an ensure_rls trigger in Supabase? What it does to new tables, how to trace it, and when to keep or drop it.
Read
-
Migrate from Lovable: What Breaks After the Move
Export worked, deploy is green, then auth emails stop and db diff shows functions you never wrote. What breaks after you migrate from Lovable, in order.
Read
-
Stripe Duplicate Charge: Two Payments or Two Fulfilments?
Two Stripe payments for one order, or a webhook processed twice? Find which path fired, refund safely and fix it with the right idempotency key.
Read
-
Stripe: No Signatures Found Matching the Expected Signature
Stripe says no signatures found matching the expected signature? The payment went through, but your app rejected the webhook. Find the cause in 4 checks.
Read
-
Supabase Email Rate Limit Exceeded: Cause & Fix
Fix Supabase over_email_send_rate_limit and 429 errors. Identify whether the built-in email provider, Auth endpoint or custom SMTP limit fired.
Read
-
Blank Screen in Production: At Least Three Separate Causes
A screenshot shows the symptom, not the cause. See three separate causes of a blank screen in production and what to capture before you redeploy.
Read
-
Environment Variable Changed but Production Not Updated?
Changed an environment variable in your hosting dashboard, but production still shows the old value? Here is why — and how to confirm which build is live.
Read
-
RLS Returned Zero Rows, but the Data May Still Exist
A row-level security query returns no rows and no error. Use a copy-only role comparison to separate RLS filtering from missing data.
Read
-
What Can a Web App Bug Fixing Service Repair?
See which live web app failures a bug fixing service can repair across login, payments, deploys and data, and when a rebuild is the wrong fit.
Read
-
It Looks 90% Done. Nine Preview Gaps
A working Lovable preview only proves the app works for its builder. Nine handover checks cover RLS, secret keys, Stripe, auth email and GitHub.
Read
-
When to Migrate Away from Lovable: A 5-Criterion Matrix
Score a Lovable client project on revenue, data, webhooks, acquisition and liability, and get a decision band with a first action.
Read
-
Exporting to GitHub Does Not Transfer Your Lovable App
An export moves your code into your GitHub account. Your database, users, files, secrets, DNS and deploy pipeline do not travel with it.
Read
-
How to Migrate Off Lovable: 6 Layers That Move Separately
Moved off Lovable but logins, images or webhooks broke? Check the six layers (code, runtime, data, identity, ops, editor) to find what didn't move.
Read