β‘ TL;DR If one or two fixes have failed, stop. Say where the bug is, what you expected and what happened, with a screenshot or the exact error. Then use Plan mode for the root cause, or revert.
Asking βfix itβ ten times is the most expensive way to fix nothing. Here is the cheaper route.
π Stop the Blind Retries
After one or two failed attempts, more of the same will only cost credits.
π Describe the Bug Properly
Name the page or component, what should happen, what happens instead, and paste the exact error or a screenshot.
π The Routine
In order:
- β Cap blind retries at two
- β Share the exact error text
- β Find the root cause in Plan mode
- β Revert in version history if it is tangled
β»οΈ Revert Without Guilt
Going back to a working version often costs less than another round of fixes.
π‘ Pro tip Bookmark a working version before every big change.
Stuck on a bug that will not budge? Lord of the Wix can help. β¨
β Debug a Lovable app FAQ
How many retries before changing tactics?
One or two.
What should a bug report include?
Where, what you expected, what happened and the error.
How do I find the root cause?
Use Plan mode.
What if the project is tangled?
Revert to a working version.
Do screenshots help?
Yes.
π Credit: Based on public information from the Lovable documentation. Lovable is a product of Lovable. Source: docs.lovable.dev. Lord of the Wix is an independent agency and is not affiliated with Lovable.