Lovable app launch checklist: how to test your Lovable app before launch (sign-up, email, login, checkout)
Short answer: test the published app, not just the preview. In Lovable the preview always runs your latest work, while visitors see a published snapshot that only changes when you publish, so something can work in the editor and still break for customers. Open your live address in a private window, sign up with an email address you've never used, and walk the whole path a customer takes: confirmation email, login, logout, password reset, checkout, the paid feature, Google sign-in and a phone-sized screen. Each step below says what "working" looks like.
Before you start
- Publish your latest changes. Lovable doesn't push edits live on its own. If the Publish button shows a small dot, there are changes your visitors can't see yet: click Publish, then Publish changes.
- Use your real address. Test on your custom domain if you have one, or on your
lovable.appaddress if you don't. That's the address customers will use. - Open a private (incognito) window. You won't be logged in as yourself, and old cached pages won't hide a problem.
- Use a fresh email address you can open, one that has never signed up to your app. Many email services let you add
+test1before the @ to make a new address that still arrives in your inbox; check that yours does. - Remember the data is shared. Lovable's preview and published app use the same backend and data, so the test accounts and orders you create will show up alongside real ones. Note which ones are yours.
1. Sign up and check the confirmation email
- On the live site, sign up with your fresh address and a password.
- Wait for the confirmation email. Check spam too: Lovable's own docs note that mail from new domains often lands there.
- Before you click the link, look at where it goes (hover over it, or long-press on a phone). It should point at your real domain, not
localhost, a preview link or an address you no longer use. - Click it. You should land on your live app, confirmed and able to log in.
If no email came at all, see Supabase confirmation email not arriving. Lovable also has an Auto-confirm email setting that skips the email entirely: handy while building, but it means anyone can sign up with an address they don't own, so check whether it's on before launch.
If the link opens the wrong address, your auth settings still point at the old one. On Lovable's built-in backend, Lovable updates the Site URL and redirect URLs when you publish and connect a domain. If your app uses your own Supabase project, it doesn't, and you add the addresses yourself: see Login broke after I added my custom domain.
2. Log in, log out, and reset the password
- Log out, then log back in with the same email and password. You should reach the same account, with anything you saved still there.
- Refresh the page while logged in. You should stay logged in.
- Log out and try to open a page that should be private, by typing its address. You should be sent to the login page, not shown the content.
- Use "forgot password". The reset email should arrive, its link should point at your real domain, and the new password should work while the old one doesn't.
3. Try checkout the right way for each environment
How Stripe behaves depends on how payments were added to your app:
- Lovable's built-in payments: the preview runs in test mode, where checkout only accepts test cards and no money moves. Your published app runs in live mode with real cards, and it won't take real payments until you finish the go-live steps in the Payments tab. In the preview, pay with Stripe's test card
4242 4242 4242 4242, any future expiry date and any 3-digit CVC. Lovable shows a test mode banner in the preview only, so it shouldn't appear on your live site. - Your own Stripe account (connected with your own key): there's no separate test environment. The key decides the mode, so with a test key everything is a test, and with a live key even payments made from the preview are real. Stripe's price IDs also differ between test and live mode, so after switching to live, check the app uses the live prices.
On the live site, do one real end-to-end purchase before you announce, for example with a 100%-off promotion code if your checkout accepts codes. A subscription's "Manage subscription" portal doesn't work inside Lovable's preview panel, so test it in a normal browser tab.
4. Check the paid feature actually unlocks
- Before paying, try to open the paid page or feature. It should be locked.
- Pay, then come back to the app without touching anything on your side. The feature should unlock on its own, ideally within seconds.
- Close the tab, log in again from a new private window, and check it's still unlocked.
If the payment went through but nothing unlocked, the app probably never heard about it: see Stripe says they paid, but nothing unlocked. If your Stripe webhook runs on a Supabase Edge Function and its deliveries fail with 401, see Stripe webhook fails with 401 on a Supabase Edge Function.
5. Sign in with Google on the live domain
If you offer Google sign-in, try it on the live address, not just in the preview. On the built-in backend, Lovable's default Managed by Lovable setup handles the Google side for you. If you switched to your own Google credentials, every address you sign in from needs its redirect URI added in Google Cloud Console, matched exactly, and selected in Lovable. An error that says redirect_uri_mismatch means one is missing: see Google sign-in redirect URI mismatch.
6. Repeat the main path on a phone
Open the live site on your phone (or use the Mobile view toggle above Lovable's preview first). Sign up, log in and reach checkout. Check that buttons aren't hidden off-screen, forms aren't cut off, and the menu opens.
If something works in preview but not live
Settings like API keys and site addresses can differ between the two: see My app works in preview but breaks in production. If your app uses its own Supabase project and a feature built on a newly added table shows "permission denied for table" or no data, see Supabase "permission denied for table" on a new table. And a clean result from a built-in security scan doesn't cover any of the steps above: see What built-in security scans miss.
Common questions
How do I test a Lovable app before launch?
Publish your latest changes, open the live address in a private window, and sign up with a fresh email. Walk the full customer path: confirmation email, login, logout, password reset, checkout, the paid feature, Google sign-in and a phone-sized screen. Test on the published app, not only the preview.
Why does my Lovable preview work but the published app break?
In Lovable the preview always runs your latest work, while visitors see a published snapshot that only changes when you click Publish. Settings like API keys and site addresses can also differ between preview and production. Publish first, then retest on the live address.
Do Lovable preview and the published app share the same data?
Yes. Lovable's docs say the preview and published app use the same backend and data, so test accounts and orders you create will show up alongside real ones. Note which ones are yours.
Should I test Stripe payments in the Lovable preview or on the live site?
With Lovable's built-in payments, the preview runs in test mode (test cards only) and the published app runs in live mode after you finish go-live. With your own Stripe key, the key decides the mode, so a live key can charge real cards even from the preview. Do one real end-to-end purchase on the live site before you announce.
How AppFirstAid helps
Our free check looks at your live site from the outside, with no signup, and checks whether your sign-up, login, pricing and checkout pages open, plus leaked keys and files left in public. A journey test, on an app you've proved is yours, does steps 1, 3 and 4 automatically: a real browser signs up, waits for the email, opens its link, logs in and tries checkout with a 100%-off code you create, with a screenshot of each step. Password reset, Google sign-in and phone screens are still worth checking by hand. Prices are on the pricing page.
Sources, read November 4, 2026: Lovable docs "Publish your Lovable project" (published app is a snapshot, changes aren't pushed live until you click Publish changes, the dot on the Publish button); "Preview and test your app in Lovable" (preview runs your latest work, preview and published app share the same backend and data, Desktop, Tablet and Mobile view toggle); "Launch your site on a custom domain" (test the live site in a private window and sign in once on the new domain); "Email authentication for your app" (confirmation and reset emails, Auto-confirm email, check spam, hourly sending limit); "Users and authentication" (Site URL and redirect URLs updated automatically on the built-in backend, not for your own Supabase project); "Add payments to your app" (test mode in the preview, live mode on the published app, go-live steps, test mode banner only in the preview, customer portal not in the preview panel); "Connect your own Stripe account" (key decides the mode, live key in the preview charges real cards, test card 4242 4242 4242 4242, price IDs differ between test and live); "Add Google authentication to your app" (Managed by Lovable default, exact redirect URIs for your own credentials). Lovable may change these details.
Check your live app in under a minute
AppFirstAid's free check looks at your live site from the outside: leaked keys, files left in public, safety settings, and whether your sign-up, login and checkout pages open. No signup. Journey tests go further: a simulated first-time user (a real browser) signs up, opens your email, logs in and tries checkout, and shows you the step that broke. Your first journey test is free.
Run the free checkSettings move around as these tools update. If a menu name has changed, look for the same words nearby. Spotted something out of date? Tell us.
More guides
- Stripe says they paid, but nothing unlocked in my vibe-coded app
- Login broke after I added my custom domain (Supabase redirect URLs)
- What built-in security scans miss in AI-built apps
- Supabase confirmation emails not arriving for new users
- Supabase "permission denied for table" (error 42501) on a new table: why it happens and the fix
- My app works in preview but breaks in production (environment variables differ)
- Stripe webhook fails with 401 on a Supabase Edge Function
- Error 400: redirect_uri_mismatch on Google sign-in (or "The JavaScript origin in the request does not match")
- Bolt app shows a database permissions error on a new table (tables private by default since Oct 30, 2026)