Lovable Pro account

You deploy Supabase Edge Functions from Lovable, they appear briefly in the dashboard, then vanish after redeployment — or start returning 401 Unauthorized errors.

What to do next: The root cause is that undeclared functions get wiped during redeployment. Every Edge Function must be listed in your supabase/config.toml:

<code class="language-toml">[functions.my-public-endpoint]
verify_jwt = false

[functions.my-admin-endpoint]
verify_jwt = true</code></pre>

Set verify_jwt = false for any endpoint called by external services (webhooks, public APIs). Set it to true for internal/admin functions.

After updating, run supabase functions deploy to synchronize all functions. If Lovable's auto-deploy still skips functions, deploy manually via the Supabase dashboard as a workaround.

Your Lovable app works in the editor preview, but after deploying to GitHub Pages or a custom domain you get a blank white screen with no visible errors.

Action plan: The blank screen is caused by incorrect asset paths. Lovable uses Vite, which by default generates absolute paths that break in subdirectories. Update vite.config.ts:

<code class="language-typescript">import { defineConfig } from 'vite';
export default defineConfig({
base: './',
});</code></pre>

Check the browser console (F12) for 404 errors on .js or .css files — this confirms the path issue.

If the preview breaks after a prompt, use Lovable's "Revert" button to go back to the last working state, then re-prompt more carefully. For persistent white screens, ask Lovable: "Review the vite.config.ts file and remove any security headers that might be blocking rendering."

Execution intent: this page targets the Lovable Pro account Fix White/Blank Screen After Deploying by Setting Base Path scenario with a ready-to-use checklist.

You describe a complex feature to Lovable in a single prompt and it generates broken code, then clicking "Try to Fix" repeatedly leads to an error loop.

Execution steps: Start your prompt with: "Can you outline the steps for this feature?" Lovable will produce a step-by-step plan without writing code. Review it, then say "Now, let's build this step by step."

Structure your project as: (1) layout and pages first, (2) connect Supabase, (3) set up auth and user roles, (4) then implement feature logic. Building in this sequence prevents dependency-related breakage.

When you hit an error, instead of spamming the Fix button, prompt: "Take a step back. Analyze the error and suggest a different approach." This forces the AI to reconsider rather than patch blindly.

For UI issues, use the Edit tool to highlight the exact element and describe the change you want.

Issue:
Lovable Pro access can appear unstable when signup verification mail handling is incomplete.

What to do:
1. Confirm inbox receive, spam folder, and sender trust before activation.
2. Finish profile basics first, then run one small generation task.
3. Keep one region and one browser profile for early sessions.

Result:
Activation succeeds faster and account stability improves in daily use.

Symptom:
Lovable Pro activation works once, then session verification repeats.

Fix path:
1. Confirm account email trust and spam filtering settings.
2. Keep one stable browser profile for early sessions.
3. Avoid concurrent logins while finishing first project setup.

Expected outcome:
Session continuity improves and repeat verification drops.