Appears when: Preview works, published site fails
The generated interface is loading in Lovable’s preview context, but the published domain is exposing a different configuration, origin, authentication callback, or backend behavior. Diagnose the first live-only failed request before prompting Lovable to rebuild components.
# Save the current working previewRecord the exact preview flow and preserve the current version before new generated changes.# Repair the first live-only failureCorrect the specific origin, integration value, route, or runtime exception shown by evidence.# Republish onceAvoid stacking unrelated prompts. Publish the one verified change and repeat the same test.# Verify the custom domain separatelyTest both the platform URL and custom domain to isolate DNS and origin behavior.Preserve the current working revision, change one proven boundary, and verify the published path in a clean session.
Open DevTools in a clean session and capture the first console or network error.
What the result tells you: A domain-specific CORS, callback, cookie, or asset error identifies the boundary faster than a visual symptom.
Confirm the live build points to the intended Supabase project and uses the expected public configuration.
What the result tells you: A wrong project URL or missing public key produces broad auth and data failures.
Reload a nested route and check whether the main JavaScript bundle and route fallback return correctly.
What the result tells you: A 404 on refresh or a failed bundle creates an apparently blank application.
| Likely cause | What proves it | First safe action |
|---|---|---|
| Live origin is not allowed | A domain-specific CORS, callback, cookie, or asset error identifies the boundary faster than a visual symptom. | Save the current working preview |
| Production integration mismatch | A wrong project URL or missing public key produces broad auth and data failures. | Repair the first live-only failure |
| Client runtime error | A 404 on refresh or a failed bundle creates an apparently blank application. | Republish once |
| Route or asset publishing issue | A domain-specific CORS, callback, cookie, or asset error identifies the boundary faster than a visual symptom. | Verify the custom domain separately |
The generated interface is loading in Lovable’s preview context, but the published domain is exposing a different configuration, origin, authentication callback, or backend behavior. Diagnose the first live-only failed request before prompting Lovable to rebuild components.
OAuth, Edge Functions, CORS, or cookies recognize preview but not the published domain.
The live app points to a different Supabase project, schema, or environment value.
A generated component assumes preview data or state and throws before the live page renders.
Freeze generated changes, restore the last known working version, reproduce one request, collect the browser and platform logs, and change one layer at a time.
Preview and live domains can differ in origin, callbacks, cached assets, integration configuration, and persisted data.
Use the exact failing request or console error. Broad repair prompts can change working layers and make diagnosis harder.
Only if the problem was a stale build. Republish after correcting a proven cause, then test the production URL cleanly.
Free decision aid
Get a senior view of the constraint, the evidence you have, and the next decision that removes the most risk.
No email required for this decision aid. Dismiss once and this popup stays closed for the session.