Fix a Lovable app that is stuck before launch.

You described the product, Lovable produced screens that work when you click through them, and the first weeks felt fast. Then one of a small number of things happens. A fix for one bug breaks a screen that worked yesterday. Sign-in works for you and fails for the first person you invite. A payment goes through and the account stays locked. Or the published app behaves differently from the preview.

That does not make the app a write-off. In the apps we see, the screens and the idea are usually sound, and the unfinished part sits underneath: who is allowed to see which records, what happens after money changes hands, and how the live site is configured. An AI builder gets you working screens quickly and leaves those decisions for you to finish. Find your symptom in the table, then read the section that covers it.

When you ask an AI builder to fix an error, it changes code until that error goes away. It does not always know which other screens depended on the code it changed, and it has no memory of why yesterday's version was arranged the way it was. After several rounds the original problem is buried under the attempted repairs, and you can no longer say which change caused what.

The way out is to stop prompting for a moment. Find the last version where the main customer journey worked and write down which one it was. From there, change one thing at a time and click through the same journey after each change. If your project is connected to a code repository, every change becomes a saved point you can go back to when a later one goes wrong.

A checkout page that accepts a test card shows that the payment provider is connected. Whether your app learned about the payment is a separate question. That second step usually depends on the provider sending a message to your app after the charge, and on your app recording it against the right account. When nothing handles that message, the customer pays and nothing unlocks.

Make one purchase in the provider's test mode, then look in your database for the result. Try a declined card and a cancelled subscription too, since a demo skips both. Give email the same treatment: send a password reset and a welcome message to an address on a different email service from your own, and look in the spam folder. In the apps we see, sign-in emails often stop arriving once more than a few people sign up, until the app sends through an email service on the founder's own domain.

Keep going yourself when the problem is contained: one screen, one bug you can reproduce, a setting you can find. The checks on this page locate many launch blockers, and fixing them in the builder is reasonable when you can test the result with two accounts and restore the previous version if the fix goes wrong.

Get help when customer data may be visible to the wrong people, when money is involved and you cannot trace a payment to an account, or when you have spent several sessions on the same fault without getting closer. An engineer who reads the code and the database can usually name the cause where prompting can only guess at it. Our Diagnostic is a fixed-price written plan: we read what you have, tell you what blocks launch and in what order to fix it, and the fee is credited to the build if you go ahead with us. Your repo and accounts stay yours either way.