Lovable signup not working: how to catch it before your users do
A Lovable app can ship a broken signup page between deploys. Here is a plain-English flow check that fails when the path does.
Lovable will happily redeploy a signup form that no longer creates a user. The preview looks fine. The first person to notice is someone who tried to pay you and couldn't get in.
Write the path the way you would tell a teammate
Don't start from selectors. Start from the sentence: sign up with a new email, confirm the email, land on the dashboard. FlowCheck turns that into steps: open /signup, fill a disposable inbox, submit, wait for the confirmation message, open the link, and assert the URL contains dashboard.
Why the confirmation step is the one that rots
The form can still 200 while the email provider, the redirect URL, or the row-level policy changed. A check that only loads the homepage will stay green. A check that has to receive mail and follow it will go red the day the link 404s.
- Use a fresh inbox address per run so you are not fighting an already-confirmed user.
- Retry a failed step once. If the retry passes, call it flaky and don't page yourself.
- Point Lovable's deploy hook at the project webhook so the check runs when the deploy finishes, not the next morning.
When it fails, the alert should include the screen and a prompt you can paste back into Lovable: what the flow was, which step stopped, and the instruction not to skip confirmation just to make the test pass.