Debuggingbeginner
Fix Endless Loading
For a spinner that never resolves — usually a request that never completes or a state that never updates.
When to use it
Emergency debugging
Lovable Prompt
A screen in my project shows a loading spinner forever. Route: [ROUTE] What it loads: [DESCRIBE THE DATA] Diagnose in this order: 1. Does the network request complete? What status and body does it return? 2. If it returns an error, is the error being swallowed so the loading state never clears? 3. Is the loading state cleared in every path, including the failure path? 4. Is a condition waiting on something that will never arrive, such as a session that is not present? Fix the real cause, then make sure the loading state always resolves into either content, an empty state or a readable error.
Why it works
It targets the specific structural bug — state not cleared on the error path — rather than the symptom.
Guides that use this prompt
TroubleshootingTroubleshooting
How to Fix Row Level Security Errors
A diagnostic order for permission errors: privileges, policy existence, policy logic, then session state.
intermediate 9 minChecked 24 Aug 2026
TutorialTroubleshooting
How to Debug a Lovable Project
A repeatable debugging loop: reproduce, isolate, read the actual error, change one thing, verify.
beginner 9 minChecked 24 Aug 2026
